Two protocols compose into one discipline: DeepSCR is a governance protocol — separation of powers over any work — and FDE is the domain method it governs. Together they turn a vague AI ask into a falsifiable, evidence-grounded, certified deliverable. This page shows the principle, the flow, and a worked engagement.
DeepSCR is domain-agnostic: it could certify any work. FDE gives it engineering depth. The composition is hierarchical — DeepSCR governs FDE specialists — which is what makes the output auditable.
Separation of powers: no single agent both proposes and certifies. Each step is adversarial to the previous one.
The field method (Palantir lineage) for taking a business problem to owned, production software.
Watch the data flow through the four powers — each stage's output is the next stage's adversary. Nothing advances until it survives.
+ falsifiable claim + hypothesis treepromote ⇔ beats the gatefile·line·test the Certifier resolves on disk.written to the public hash-chained registry. Otherwise: veto → re-routed to the weakest owner.Four weighted components. Evidence is the largest — and it only counts if the cited artifacts resolve on disk (ground truth, not structure).
The Builder consults the four FDE specialists in parallel; the Certifier verifies their claims. "DeepSCR governs FDE specialists."
| Agent | Layer | Role in the protocol |
|---|---|---|
| Lead | DeepSCR | 6-Q decomposition + falsifiable claim + hypothesis tree |
| Researcher ×N | DeepSCR | Falsify hypotheses in parallel against the held-out gate |
| Builder | DeepSCR | Assemble the deliverable from the specialists; score the rubric |
| Certifier | DeepSCR | Independent Assurance Score; veto if evidence is weak |
| Scoping | FDE specialist | Sharpen the 6-Q; lock metric & cost-of-error |
| Architecture | FDE specialist | Stack / SaaS architecture from Q2–Q3, kept reversible |
| Agent | FDE specialist | Eval gate, reason codes, guardrails, red-team cases |
| Production | FDE specialist | Runbook, observability, cost ceiling, compliance |
Every engagement states a claim a held-out test could refute — not a vibe.
The proposer never certifies. The Certifier can veto the Lead's optimism.
Synthetic structure earns nothing; cited file·line·test must exist.
Every certification lands in a hash-chained registry anyone can re-verify.
Install the Skill, point it at real code, and read the certified result.