Operating stack hub

This is the hub for how Exiid runs: borrowed frameworks with attribution, proprietary gates, studio tools, model routes, and eval harnesses. Everything maps to RECON or RAID, with a receipt on every row.

Who this is for

For: partners and buyers who want process transparency before they send a brief.

Useful when: you need to see what we actually run, not a framework slide deck.

What must be true

Transparency without receipts is theater. Every item in the operating stack answers four questions:

Question	The bar
Attributed	Borrowed frameworks name the source
Mapped	Each item ties to RECON, RAID, or cross-cutting gates
Tiered	Runs, Install, or Bench, never vague "we use AI"
Receipted	Link to memo, venture, or live artifact

01 — Three layers of honesty

Frameworks are how we think: JTBD, Theory of Constraints, Shape Up, and others credited in full on Method.app.

Tools are what we run or install: six layers from intelligence research through ops and security, tier-labeled.

Harnesses are what we own: context rails, eval golden sets, runtime checks, blast-radius caps. Models are rented; harnesses compound.

02 — RECON and RAID mapping

RECON (Discover + Validate) is decode, demand tests, and go/no-go before build capital moves.

RAID (Build + Launch + Scale) is instrumented product, measured launch, and scale only where unit economics hold.

Cross-cutting workflows (Brief Desk, eval loop, kill archive) span both.

03 — Where to read next

Topic	Memo
JTBD in transfer work	JTBD in model transfer
Studio tools by layer	Enterprise tooling stack
Models, agents, harnesses	AI models and harnesses
Bottleneck thinking	Theory of Constraints for operators
Sprint appetite	Shape Up at Exiid
Instrumentation	North Star and instrumentation

Receipts

• Method.app operating stack: live index with tier badges
• AI Systems Design: Autonomy Ladder and Approval Line
• One operator, many agents: how the stack runs day to day
• Public kill archive: when gates fail, the memo stays public