Docs surface

Docs that point to the real package and service surfaces.

The docs layer should make the stack easier to enter, not duplicate it. These paths point directly to the install, contract, runbook, and release materials that already exist in the live repos and packages, so people can move from marketing to operation without a second translation layer.

Runtime docs

xytara docs

xytara currently exposes 5 durable public docs and entrypoints across install, quickstart, contract, operations, and release paths.

  • README.md
  • START_HERE.md
  • FINAL_CONTRACT.md
  • SERVICE_CONTRACT.md
  • PROGRAM_STATUS.md
  • OPERATIONS_RUNBOOK.md
  • xytara start-here
  • xytara release --summary
  • xytara run --help
Proof docs

xoonya docs

xoonya currently exposes 6 durable public docs and entrypoints across install, proof walkthrough, contract, operations, and release paths.

  • README.md
  • START_HERE.md
  • FINAL_CONTRACT.md
  • SERVICE_CONTRACT.md
  • PROGRAM_STATUS.md
  • OPERATIONS_RUNBOOK.md
  • xoonya start-here
  • xoonya release --summary
  • xoonya review --help
Entry paths

Proof and launch references

These are the first public pages we expect builders to touch when they want the live stack, the proof side, and the launch route in one pass.

Use these first

Fastest public references

If someone arrives from npm, GitHub, CLI, or a chat environment, these are the shortest paths to a real understanding of the system.