GNPL expresses warranted accounts over evidence. Lithoglyph is the intended
source of durable evidence and provenance; Glyphbase is the intended application
surface. Their owning repositories are hyperpolymath/lithoglyph and
hyperpolymath/glyphbase. The umbrella repository coordinates this relationship.
The direct-evidence kernel, .gnpl projection parser and gnpl executable run
against an imported gnpl-evidence-v1 snapshot. They construct ordered accounts,
apply focalization and a declared threshold, retain rival accounts, and
re-evaluate a projection after a hypothetical source withdrawal.
See the runnable slice for commands, examples, tests and the exact warrant rule. The example JSON is a fixture. It is not a journal export produced by a live Lithoglyph adapter.
Lithoglyph evidence/journal
| read-only snapshot adapter: next integration
v
GNPL evidence snapshot + declared projection
| implemented direct-evidence narration kernel
v
Account with warrant trail, or explicit refusal
| durable account storage and rendering: later integration
v
Glyphbase
Selection and storage validation remain private machinery. GNPL has no fixed public intermediate language or promised compilation route through the existing storage modules.
| Snapshot field | Required mapping and check |
|---|---|
Snapshot identity and revision |
Read a consistent evidence state and identify it reproducibly. A historical account refers to that state; later withdrawal requires a new evaluation. |
Evidence identifier and structured claim |
Preserve distinct source assertions, including disagreements. Each identifier is unique within the imported snapshot. Subject/slot/value matching in the first fragment assumes a single-valued slot within each account. |
Source and rationale |
Preserve attribution and a readable rationale. Journal membership, a nonempty reason or an ABI proof blob alone does not establish semantic warrant. |
Audience |
Derive visibility from an explicit policy. The current local importer trusts supplied audience lists; it provides no actor authentication or access service. |
Declared confidence |
Provide an integer in 0–100 with its interpretation documented. The kernel compares it to a threshold; it does not average PROMPT dimensions or derive a probability, entrenchment ordering or winner. |
Withdrawal |
Map retractions to evidence status without rewriting historical snapshots. Test a cited withdrawal, an unrelated withdrawal and revision consistency. |
The existing ABI/FFI structures are potential integration components. Their presence does not establish that these mappings, durable writes or read paths are wired. In particular, the proof registry’s refusal of unimplemented verifiers must remain visible to any adapter that asks for certificate checking.
-
A forensic account can show the source, rationale, stance and declared score alongside each assertion, making its dependency on recorded evidence inspectable.
-
Conflicting source assertions can support separate rival accounts. The first fragment detects rival values for a subject/slot and does not adjudicate truth.
-
A hypothetical withdrawal can identify when this particular account loses its warrant. An invalidated account is not a finding that its claims are false.
-
Glyphbase can eventually render an ordered account and its warrant trail, including revision and withdrawal results, once the durable path is implemented.
The current slice does not implement causal reconstruction, event-time queries, general argumentation, automatic account search, derivation chains or confidence composition. Those require further semantics; they are not implied by the source’s rationale text or by passing storage tests.
Create evidence through a real Lithoglyph interface, import a consistent snapshot, and narrate an account using that imported evidence. Then withdraw one cited item through the same store and show that a fresh projection refuses it while the historical account remains tied to its earlier snapshot. A parallel control must withdraw an uncited item and preserve the account.
Only after that path passes should Glyphbase claim a durable account workflow. The local counterfactual command already exercises the corresponding kernel behaviour without changing the input file.