# Glyph Standard

## Institution and category
- Institution: Glyph Standard.
- Category: Answerable Computing.
- Compute is becoming its own customer.
- In Answerable Computing, the party relying on machine work can retain the transaction record and evaluate the evidence under its own policy.

## Shipped system and stable format
- Glyph Standard develops Bulla, its shipped system for Answerable Computing. ActionReceipt is Bulla's stable transaction format.
- Published package: bulla==0.48.0.
- Install: python -m pip install "bulla==0.48.0"
- Task interface: https://glyphstandard.com/bulla/llms.txt

## Research boundary
- Current implementation mechanisms and experiments are repository-source research; they are not capabilities of the released Bulla package.
- Evidence frontier: Project-operated research · W0 independent witnesses · D0 external reliance decisions · no real settlement.
- Research: https://glyphstandard.com/research

## Retained result
- The retained packet reproduces the published judgment from packet members alone; repository input and prior receiver state are not supplied, installed Bulla is not used, and no Glyph Standard route is requested.
- Authentic fork evidence alone establishes the witness conflict but does not authorize propagation.
- When an accepted correction notice is added, the receiver recomputes the declared recheck set from retained artifacts.
- Transaction record: sha256:ce559fe4a81687a4eec99f33c6e04bab31e23e46af87091059ef3c3acb3e1c95
- Review control: 10000 review-all; 5000 required review; 0 incomplete-lineage decisions cleared.
- Reproduce: https://glyphstandard.com/research/retained-evidence

## Never infer
- This definition names Glyph Standard's program jurisdiction. It does not imply that repository-source research is a capability of the released Bulla package, complete observation, correction truth, automatic enforcement, legal effect, independent operation, or adoption.
- Repository-source research profiles are outside the installed package unless a published release explicitly includes them.
- Formal verification applies to the stated mathematical object; empirical identification, conjecture, correction, and released-package capability remain separately labelled.
- This is a dated category thesis, not a measurement of present transaction volume, Bulla adoption, or autonomous economic activity.
- These rules are profile-relative verifier properties over supplied records; they do not establish complete observation, worldly causation, legal effect, actual settlement, or complete dependency capture.
- The witness covenant is an experimental source implementation over project-authored keys, checkpoints, challenge records, allocations, authorities, and Test-ledger reports. It does not establish independent operation, receipt truth, complete observation, custody, collectibility, deterrence, actual recovery, real settlement, production operation, or a witness market. It is not part of the installed Bulla package.
- The Reliance Map is an experimental source implementation over a project-authored synthetic graph, correction notice, keys, and context. Its result is relative to the accepted declared graph. It does not establish correction truth, complete worldly dependency capture, action safety, rollback, consequence authorization, independent operation, production use, or adoption. It is not part of the installed Bulla package.
- A qualified D record establishes one signed receiver-policy computation over supplied records and an attributed intake determination about organizational control. It does not mathematically establish organizational independence, provider-claim truth, policy suitability, actor time, or any later payment, deployment, control grant, or handoff.
- A qualified W record establishes one separately controlled witness operation over the submitted public release records. It does not cryptographically establish organizational independence, receipt truth, occurrence, continuing availability, policy compliance, production fitness, bond value, recourse, or a witness market.
- The packet establishes local historical reproduction under supplied verifiers and receiver contexts. Its launcher blocks enumerated Node network interfaces but does not establish operating-system network isolation. It does not establish freshness, current revocation or external state, independent operation, occurrence, worldly truth, custody, settlement, causal independence, or completeness beyond the accepted declaration.
- The drill is a project-operated, fixture-bound evaluator reachability result. It does not establish live H100 execution, worldly occurrence, provider identity, organizational independence, production reliance, legal effect, enforceability, collectibility, external custody, real settlement, or completeness outside its declared packet and receiver policy.

## Machine interfaces
- Evidence: https://glyphstandard.com/evidence
- Status: https://glyphstandard.com/status
- Public claims: https://glyphstandard.com/claims.json
- Comprehensive institutional surface: https://glyphstandard.com/llms-full.txt
- Bulla task surface: https://glyphstandard.com/bulla/llms.txt
- External reliance evidence: https://glyphstandard.com/evidence/reliance-decisions.json
- Independent witness evidence: https://glyphstandard.com/evidence/witnesses.json
- Status: https://glyphstandard.com/status/status.json
- Publication set: https://glyphstandard.com/public-surface.json. Pin surface_root; reread governed surfaces before relying after it changes.