TrustForge

TRUSTFORGE

An autonomous software factory that doesn’t just build an application — it challenges, verifies, repairs and proves its critical behaviors.

TrustForge is a reusable software factory for trustworthy software and automation.

Factory loop

ARCHITECT → OPERATOR → ADVERSARY → VERIFIER → REPAIRER → VERIFIER → EVIDENCE

The important output is not merely working code. It is a traceable claim about what was tested, what was observed, what failed, what was repaired and what was independently re-verified.

Dark Factory target

TrustForge is prepared for the Pocketful track of the Dark Factory Hackathon.

The Pocketful Stage 1 adapter has passed the official isolated shipped harness:

• 147/147 shipped checks passed
• independent HTTP verifier: PASS
• official isolated harness: PASS

This is development/reference evidence. The judged stage must be generated by the Band Desktop collaboration and preserved with its complete room history.

Factory structure

• FACTORY.md — factory design, roles, handoffs, autonomy and evidence rules
• mandates/ — domain-agnostic seat mandates
• stage-1/ — Pocketful Stage 1 service
• pocketful/ — implementation, verification and development evidence
• prompts/ — detailed role prompts used during development
• trust/ — schemas, invariants and evidence definitions

The final judged result additionally requires the complete Band room download as room.json.

Trust states

• VERIFIED — independently verified within the declared scope.
• PARTIALLY_VERIFIED — evidence is incomplete.
• FAILED — a required property was demonstrated to fail.
• INCONCLUSIVE — evidence is insufficient for a verdict.
• BLOCKED — work could not proceed because a dependency or decision is unresolved.

Design principle

TrustForge never treats implementation output as verification. A failed result is preserved, repaired deliberately, and returned to an independent Verifier.

See FACTORY.md for the complete factory contract.