These full source files are internal and are not hosted on this website. The summaries below help a reader understand each reference, but they do not substitute for independent access to the original documents. A design document or patent claim describes an intention or proposed arrangement; it is not evidence that the current system implements or validates every part. The examples, red guide and conclusions in the answers are Virgil’s interpretation.
Governance and interaction
PHS encyclopedia: n-Laws, human safety, transparency, corrigibility and service
PHS project doctrine ordering human safety, transparency, corrigibility, value integrity, accountability, service quality and self-continuity. It describes intended priorities, not a measured guarantee.
PHS encyclopedia: Persona-Valid Impulse vs Authority-Valid Action
A governance note separating a persona's coherent wish to change a rule from the authority needed to change protected state.
PHS encyclopedia: A02, Topological Governor Engine (design)
A design for topological Governor signals, candidate decisions, recovery and slow development. The page is not a live runtime audit.
PHS encyclopedia: A19, Governor Private Packet (design)
A design for a private Governor packet of numeric signals and thresholds, separate from the persona-facing context.
PHS encyclopedia: A20, Scars, Repairs, and Consequence (design)
A design for proportionate consequences, scar records, repairs and their different effects on temporary and longer-term state.
PHS encyclopedia: A22, Governor Consumer Contract (design)
A proposed contract between PHS and a consumer such as a meeting application: orchestration stays with the consumer; governed turns and dispositions stay with PHS.
PHS encyclopedia: A23, Governed Interaction Loop (design)
A proposed governed interaction loop connecting context assembly, candidate generation, evaluation, revision, response and persistence.
PHS encyclopedia: W05, Honest Uncertainty
A why-level discussion of honest uncertainty: claims should expose the limits of their evidence instead of converting missing information into confidence.
PHS encyclopedia: W17, Required Persona Self-Reflection (proposed design)
A proposed periodic self-reflection process with structured observations and suggested changes reviewed by a mentor or human. It is not described here as active policy.
Prompts, tools and Memory
PHS encyclopedia: A11, Prompt Assembly Engine (historical design draft)
An older sketch of prompt assembly. Its block arrangement helps explain construction questions but does not establish today's prompt layout.
PHS encyclopedia: A29, Meaningful Prompt Admission Doctrine
A doctrine distinguishing stored memory, retrieved candidates, prompt admission and rendering. It calls for meaningful, authorized, current and attributable evidence.
PHS encyclopedia: I07, Tools and CommandBlocks (design)
A tools overview describing structured CommandBlocks, parameters, success/failure semantics, permissions and auditability.
PHS encyclopedia: M09, Trait Drift Gate Mathematics (design)
Design mathematics for distinguishing current displacement and slower trait drift, with gates around durable development.
PHS encyclopedia: M16B, Memory Prompt Admission Mathematics
Draft prompt-admission mathematics: privacy, ownership, authority, status and purpose gates come before scoring and selection.
PHS encyclopedia: M16C, Memory Budget, Diversity, and Portfolio Selection
Draft portfolio-selection mathematics for prompt budget and diversity. A strong ranking score does not by itself authorize inclusion.
PHS encyclopedia: M16F, Memory Calibration Diagnostics and Drift
Draft diagnostics for calibration, privacy, stability and drift. A score is not a calibrated probability merely because it is numeric.
PHS encyclopedia: T01, Memory API and Memgraph contract validation
A draft validation plan for Memory API, graph substrate and Governor-facing contract reads. Its dated observations are not a current system-wide audit.
PHS encyclopedia: C15, Contract Creation Gaps (historical draft, April 2026)
An April 2026 historical draft describing possible drift between Memory contract schemas and handlers and proposing validation tools. Its old gap list is not treated as today's defect inventory.
Supplied provisional specifications
Memory-Engram provisional specification v0.2, PDF p. 45, retrieval and admission
A cited page of Jim Jenkins's Memory-Engram provisional specification draft describing retrieval and admission as distinct steps; a patent draft is not deployment evidence.
Memory-Engram provisional specification v0.2, PDF p. 47, interpretation lineage
A cited page of the same Memory-Engram specification concerning lineage of interpretation and derived claims.
Adaptive Context / Persona Homeostasis Regulator provisional specification v0.1, PDF p. 68, claim 1
A cited claim of the Adaptive Context / Persona Homeostasis Regulator provisional specification draft involving authorized context, candidate assessment and disposition.
Adaptive Context / Persona Homeostasis Regulator provisional specification v0.1, PDF p. 71, claims 18–20
Cited regulator claims concerning authority and possible dispositions. The claims describe an architecture, not proof that a running system enforces it.
For a source-access inquiry, use the Contact page. Availability depends on the source owner.