DEPLOYDatabase

DEPLOY

Framework in action

This is the index of DEPLOY's framework-in-action work. Three classes of editorial output operate under the verified-vs-claimed framework: framework-in-action narratives that apply the framework to specific events, correction narratives that document where we got a record wrong and how we surfaced the catch, and methodology pillar essays that define the framework constructs at canonical reference depth.

For the core methodology canon, see /methodology/what-verified-means. For the corrections journal at editorial-anchor depth, see /corrections. For the cluster surfaces, see /explainers.

Framework-in-action narratives

Specific events read through the verified-vs-claimed framework. Each narrative anchors a worked example of the framework discipline at a primary-source verification depth.

Correction narratives

Where we got a record wrong and how we surfaced the catch. The recursive application of the verified-vs-claimed framework on DEPLOY's own corpus.

Methodology pillar essays

Canonical reference essays that define the framework constructs. These pillars live on the explainer surface; the operating constructs they define drive every framework-in-action narrative and every correction above.

  • How DEPLOY verifiesmethodology-canonical

    The methodology editorial canonical; four-tier verification protocol applied across registry + signals + consumer surfaces.

  • 5 primary tiers + 2 secondary tiers + 1 aggregator tier + 1 unverified tier; per-claim source-quality discipline operationalized.

  • The framework operates at sub-fiscal-period, within-product-family, and per-feature granularity, not just at the entity layer.

  • Autonomous-execution + AI-augmented operator-controlled + replacement-robotics teleoperated + assistive co-pilot; surgical cohort canonical worked example.

  • Captive brain integration (1X Redwood) vs third-party brain integration (NVIDIA GR00T, Skild AI); humanoid + AV brain-provider integration gradient.

  • Four-dimension actuarial framework (Dim 1 incident outcome_class + deployment exposure_hours; Dim 2 manufacturer counterparty risk; Dim 3 supply-chain component failure; Dim 4 cross-jurisdictional regulatory state).

  • Four-state partnership lifecycle framework (announced + active + dissolved + unverified-current-state) at relationship-graph granularity.

  • Five-structure acquisition taxonomy (full + asset_purchase + acqui_hire + license_and_hire + spac_merger) + four-state valuation_basis discipline (exact + reported + undisclosed + contingent).