ryan-brosas Pi Upstream Foundation
Foundation contract
This is a cold, source-specific foundation, not an operational procedure. It is historical, revision-pinned evidence rather than timeless guidance. Current project source, tests, requirements, and runtime behavior outrank this projection and decide what ships.
Provenance and revision
- Source record:
pi-upstream; portable upstream identity, license, coverage caveats, and retrieval history are preserved in the index. - Recorded revision:
main@4af9d21d3b4d664e4a29fcabfec85171077248e3. - Full provenance, coverage caveats, boundaries, and preserved evidence:
references/index.md.
Topic map
- Representative topics: Agent loop; Compaction & summarization; Session & boundary; Terminal UX; Tool & skill loading (drift pass 2); Self-update & install lifecycle (drift pass 3); SQLite session backend (passes 4–11).
- Scope and retrieval questions:
references/index.md#use-this-for. - Complete capsule chooser:
references/index.md#load-the-matching-source-dump. - Detailed grouped map:
references/index.md#capsule-map. - Source limitations and portability boundaries:
references/index.md#boundaries.
Retrieval
Open the index, choose one capsule matching the active question, and load only that capsule. Revalidate its cited source and revision before relying on it. Do not bulk-load the inventory, treat historical claims as current truth, or apply this foundation as a procedure.