DRAFT
SPEC-DS-01
CERTIFIED DESIGN
The data contract passed from OAD to COS when a design is approved for production. Fields: design_id, version, bill_of_materials, production_steps, ecological_flag, itc_access_cost, design_lineage.
DRAFT
SPEC-DS-02
LABOR EVENT
Emitted by COS when a participant completes verified work. Consumed by ITC (to issue credits) and FRS (to update labor summary). Fields: participant_id, task_ref, hours_verified, skill_tier, itc_credits_issued, ecological_flag.
DRAFT
SPEC-DS-03
MATERIAL CONSUMPTION EVENT
Emitted by COS when materials are consumed in production. Consumed by ITC and FRS. Fields: material_id, quantity_consumed, ecological_flag, source, production_ref.
DRAFT
SPEC-DS-04
ITC LEDGER ENTRY
Append-only record of every credit transaction. Fields: entry_id, timestamp, participant_id, entry_type (LABOR_EVENT | DECAY_APPLIED | ACCESS_REDEEMED | NEED_ADJUSTMENT), amount, balance_after, source_ref.
DRAFT
SPEC-DS-05
FRS SIGNAL PACKET
The structured summary emitted by FRS and routed to CDS. Contains labor_summary, materials_summary, itc_summary, qa_summary, ecological_summary, findings[], and recommendations[]. This is the primary output of the feedback loop.
DRAFT
SPEC-DS-06
DECISION PACKET
The structured output of a completed CDS governance cycle. Fields: decision_id, issue_ref, outcome, rationale, dissenting_positions, dispatch_targets[], implementation_constraints, review_trigger.
PENDING
SPEC-IF-01
OAD → COS INTERFACE
API contract for design certification handoff. Versioning policy, authentication requirements, error handling, and retry behavior for the CertifiedDesign data transfer.
PENDING
SPEC-IF-02
COS → ITC INTERFACE
API contract for labor event and material event submission. Batch vs. streaming delivery. Idempotency requirements for the append-only ledger.
PENDING
SPEC-IF-03
FRS → CDS INTERFACE
The feedback loop interface — the most architecturally critical seam in the system. Delivery guarantees, signal packet versioning, recommendation routing, and CDS acknowledgment protocol.
PENDING
SPEC-STACK-01
TECHNOLOGY STACK DECISION
The Phase 0 technology stack decision — programming languages, database, API protocol, deployment model — is a foundational governance decision that must be made before Phase 1 code is written. Open for community deliberation now.
SPECIFICATIONS NEED CONTRIBUTORS
Interface contracts and the technology stack decision are the highest-priority Phase 0 deliverables. Systems architects, backend developers, and protocol designers are especially needed right now.