Inside Sercrod

Status: implemented documentation and navigation layer.

Inside Sercrod explains how the current system fits together. It is not a second directive manual, a replacement for the runtime specification, or a site source. Canonical content is English Markdown in this directory.

Start here

1. Read What Sercrod Is for the responsibility boundary.
2. Read Sercrod Core, then its Host and Scope, Data and Evaluation, Rendering Model, Actions and Results, and Updates and Redraw route.
3. Read The Runtime Flow to connect those Core concepts.
4. Read Lifecycle, Ownership, and Security for cleanup, diagnostics, safe results, and trusted-content boundaries.
5. Read Capabilities and Adapter Architecture only when Core hands work beyond its boundary, then Platforms and Packaging.
6. Follow the linked runtime, manual, reference, sample, and test evidence for any detailed claim before changing behavior.

For a task-oriented first entry, start with the existing AI Start Here (docs/spec/ai-start-here.md). It remains a lightweight route into the detailed material; it is not replaced by this guide.

For a purpose-driven change or review route, use the AI Reading Guide.

Authority and status

For current behavior, use the applicable implementation, canonical manual, and test evidence before a conceptual page:

dist/sercrod.js and dist/adapters/
  -> dist/man.json
  -> focused tests and samples
  -> detailed reference pages

Status labels apply to individual claims:

• implemented — supported by current implementation, manual, and relevant evidence.
• settled contract — approved behavior that must still be checked against implementation before it is presented as available.
• environment-dependent — varies with a browser, WebView, native platform, permission UI, or external service.
• deferred, planned, and historical — respectively excluded, proposed, or retained for provenance rather than current guidance.
• uncertain — not publishable as an implementation claim until the evidence is reconciled.

What this layer does not do

Inside Sercrod does not invent a directive, event, public Core API, permission, adapter operation, or platform contract. It links to detailed directive and adapter references rather than copying their catalogues or external-library APIs.

Evidence

Status: implemented documentation layer.

Evidence: docs/spec/inside-sercrod-plan.md, docs/spec/runtime.md, canonical manual dist/man.json, and the public reference index.