Machine-readable contracts for discovery and exploration.
Start with the discovery manifest, read the skill contracts, then follow a declared neighbor. These documents belong to the operator-maintained FCS-4.0 publication family. They distinguish implemented interfaces, experimental specifications, and historical records.
Meaning becomes a contract when its inputs, outputs, and limits are explicit. A contract alone does not establish trust or prove that a claimed capability works.
Trust scoring, lineage verification, T/D/S coordinate traversal, and registration are not implemented. Verification and registration requests return HTTP 501. There is no local ABF feed configured.
Current capabilities, dependency URLs, and implementation limits.
FCS-4.0Three implemented interfaces and one explicitly unavailable trust interface.
FCS-4.0Declared neighboring domains and relationships. Follow links to explore; no coordinate traversal is implemented.
FCS-4.0Current request and response schemas, methods, and runtime limits.
FCS-4.0Preserved dated assessment; it does not establish current trust.
Historical snapshotExperimental PHI.108 model. Its multiplier ranges are declarations, not measured performance.
Experimental specificationHistorical FCS-3.0 topology; use the current topology above.
Superseded topologyHistorical FCS-3.0 interface document; use the current invocation registry above.
Legacy contractThe demo reports local structural checks. It performs no trust verification and makes no external requests.