One declared interface, many compatible agents
Publishers should not have to let every agent independently scrape, guess and reinterpret their public information.
Preserve vocabulary
Your native names and lexical values remain visible beneath any shared semantic view.
Declare policy
State attribution, refresh, access, effect and revocation rules explicitly.
Reduce waste
A promoted typed representation can be compiled once and reused without browser execution for every query.
Correct the record
Publisher approval, correction and revocation are separate states, never inferred from technical availability.
Planned publisher path
- DescribeNative concepts, public resources, read-only operations and attribution.
- ValidateCheck bounded schemas, effects, evidence requirements and conformance.
- PreviewInspect native and semantic values, mappings and generated bindings.
- Verify originProve control separately from technical compatibility.
- Publish and monitorExpose the interface, health state, corrections and revocations.
The complete publisher CLI and origin-claim flow are funded roadmap items, not currently released capabilities.
Availability is not authority
TWIRX keeps publisher identity, policy review, technical stage, health, adapter trust and mapping trust as separate dimensions. A working endpoint cannot declare itself approved, authoritative or canonized.
Join a publisher-readiness pilot
The initial pilot is read-only and bounded. It helps one publisher document an existing API, feed, JSON-LD or structured public surface while retaining attribution and correction rights.