Content metadata ledgers

Article collections and schema document folders can contain a rebuildable .rigel-collection.json. Source JSON remains authoritative. Ledgers store version 1 metadata with a configuration fingerprint, storage slugs and exact Git blob SHAs. Article entries contain frontmatter rather than bodies; document entries hold identity, route and list metadata plus reference identities. Reading content never creates remote ledgers.

GitHub sign-in verifies access and reads branch/tree identities and existing article ledgers. Document ledgers load when their group opens. Pages defaults to All pages, requesting metadata for all non-shared groups in the selected content language. Selecting Core, a named category or a document-type list narrows the request to that group.

Matching ledgers avoid source-body downloads for lists. Missing or stale metadata reconciles progressively within the requested group, with progress, cancellation and retry. Selecting a document reads its exact source and recursively loads its actual reference dependencies. Selecting an article, copy page or menu loads that selected source rather than all its neighbors. Forms remain blocked until required content validates.

Search and WebMCP discovery use storage identities and currently loaded metadata without starting body reconciliation. Titles can be unavailable until their group opens. Browser-tool results report metadata completeness separately. Neither is full-text body search. Content-language search scope remains a separate preference.

Transport and file cache

Requested uncached text blobs share read-only GitHub GraphQL queries, bounded to 64 aliases and an estimated 2 MiB per query, with at most four active transport requests. Each result must match its expected SHA and complete text. Missing, truncated or invalid aliases fall back individually to REST; authentication, rate-limit and request-wide failures stop rather than triggering a retry storm. Writes keep the REST tree/commit flow.

IndexedDB stores SHA-checked text scoped to the verified account and repository/branch/schema configuration, with limits of 128 text entries and 16 MiB. Bounded memory caching covers unavailable or full storage. Reload still verifies access and reads the current branch/tree. Credentials are excluded from cache keys and values. Media bytes and generated thumbnails also use persistent caching; full previews and downloads use original bytes.

Clear File Cache in Settings > Advanced > Maintenance invalidates pending generations and clears memory, persistent files and preview URLs. Late reads cannot repopulate a cleared generation. Drafts, settings and sessions remain intact. Failed clears are reported and retried before later persistent reads. Sign-out and account changes purge private cached content.

Save and reindex

GitHub Save/create/delete writes the selected document or article and its affected ledger in one atomic, non-forced draft commit. Route uniqueness and reference checks may need metadata outside the open group; partial lists are not treated as complete validation indexes. Conflicts stop writes and preserve the draft.

Confirmed Settings > Advanced > Maintenance > Reindex all content rebuilds document and article ledgers in one draft commit. It does not change source content or publish. Canceling before commit leaves no partial ledger commits; an uncertain commit needs retry verification. Source JSON is limited to 1 MiB and ledger JSON to 16 MiB.

Collection tables no longer have a separate Refresh action. Use the explicit Reindex all content operation when you need to rebuild ledgers; opening content still reconciles stale metadata as needed. Maintenance shows a general loading line, static with reduced motion. Developer mode adds identifiers and counts, while completion and errors remain visible in either mode.

Local and demo modes

Local filesystem loading remains eager. Local reindexing rebuilds both ledger kinds, with atomic replacement per file rather than a multi-file transaction. Local document saves do not automatically update ledgers; later GitHub access detects changed SHAs and reconciles metadata read-only, or explicit maintenance rebuilds it. Demo mode cannot write or reindex.

See GitHub publishing for shared drafts, authorization and deployment, or Media for repository assets.

Documentation

On this page