Operations Introductory 2 minute read Updated 2026-06-26 UTC

Docs as durable memory

How the /docs folder replaces a memory wiki for original report preservation and source routing.

Research statusCurrent project memory design Publication statePublished Reviewed byMichael Kappel Source reports3

Principle

The /docs folder is the durable long-term source memory for this project. It holds the original reports exactly as supplied. The public curriculum draws from them, but does not replace them.

This design avoids a second memory wiki. The project already has source documents, a manifest, curated content, and typed .uai hot memory. Adding a wiki would duplicate concepts and create another place for stale truth to accumulate.

Source memory layers

LayerFunction
/docs/*.mdoriginal reports, byte-preserved
docs/manifest.jsonfilename, slug, category, size, SHA-256
.uai/docs-source-ledger.uairouting note and promotion rule
content/pages/**.mdcurated public synthesis
.uai/report-synthesis.uaicompact accepted synthesis for agent startup

Promotion rule

A report claim is not automatically current truth. It becomes current truth only when promoted into a curated page, code, tests, release notes, decision record, or typed .uai file.

pseudocode
FUNCTION promote_report_claim(report_slug, claim, target)
    report <- LOAD_DOCS_MANIFEST_RECORD(report_slug)
    VERIFY_SHA256(report.path, report.sha256)
    review <- HUMAN_OR_EDITORIAL_REVIEW(claim)

    IF review.accepted
        WRITE_TO_TARGET(target, claim, provenance = report.slug)
        RECORD_PROMOTION(report.slug, target, review.reason)
    ELSE
        RECORD_REJECTION(report.slug, claim, review.reason)
    END IF
END FUNCTION

Why not direct browsing

The reports are stored in the site ZIP so they are not lost, but direct directory browsing is not the publication mechanism. The application renders and downloads reports only by manifest slug. This preserves integrity and avoids exposing private project folders as a directory index.

Adding a new report

Copy it into /docs, compute exact byte size and SHA-256, add a manifest entry, connect the slug to curated pages, and run the build. Never overwrite an original report while keeping the same digest.

Source reports used for this guide

These reports are preserved verbatim in the site archive. The guide above is an editorial synthesis and may narrow, qualify, or reorganize claims from the source material.