Skip to content

Rebuild schemas reference page with protocol-ready documentation#249

Merged
GsCommand merged 1 commit into
mainfrom
codex/rebuild-schemas.html-for-dev-reference
May 21, 2026
Merged

Rebuild schemas reference page with protocol-ready documentation#249
GsCommand merged 1 commit into
mainfrom
codex/rebuild-schemas.html-for-dev-reference

Conversation

@GsCommand
Copy link
Copy Markdown
Contributor

Motivation

  • Convert public/schemas.html from a minimal/unstable stub into a senior-developer protocol schema reference page with correct nav/footer and infrastructure-level guidance.
  • Remove stale/incorrect IPFS/CID claims and provide a clear placeholder for future canonical publication without inventing any CIDs.
  • Present canonical proof contract details and developer-oriented guidance (paths, validation vs verification, example snippets) while preserving the existing visual/header/footer style used by other docs pages.

Description

  • Replaced the contents of public/schemas.html with a full protocol-ready reference page that matches the site header/nav/dropdown/footer style used by other rebuilt docs pages.
  • Added sections: hero and production proof status, schema system overview cards, canonical proof envelope with canonical values (metadata.proof.canonicalization = "json.sorted_keys.v1", metadata.proof.hash.alg = "SHA-256", metadata.proof.signature.alg = "Ed25519", metadata.proof.signature.kid = "vC4WbcNoq2znSCiQ", metadata.proof.signer_id = "runtime.commandlayer.eth"), Trust Verification v1 family and live verbs, expected file/path model table, schema validation vs cryptographic verification, capability expansion model, developer usage flow, and compact request/receipt snippets.
  • Removed explicit/stale CID values and replaced them with a clearly marked IPFS/CID publication status block that states publication is pending (no invented CIDs).
  • Preserved constraints: no schema files, API routes, or unrelated pages were changed; visual direction and component styling were kept consistent with other docs.

Testing

  • Ran npm install successfully.
  • Ran npm test and all automated tests passed (26 tests passed, 0 failed).
  • Attempted npm run build but the repository does not define a build script, so no build step was executed.

Codex Task

@vercel
Copy link
Copy Markdown

vercel Bot commented May 21, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
commandlayer-commandlayer-org Ready Ready Preview, Comment May 21, 2026 8:13pm
commandlayer-org Ready Ready Preview, Comment May 21, 2026 8:13pm
commandlayer-org111 Ready Ready Preview, Comment May 21, 2026 8:13pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant