Appendix E: Formal Definitions and Glossary
| Term | Definition |
|---|---|
| Claim | A precise, evaluable statement about a subject within a defined context. The atomic input to the Verification Engine. |
| Subject | The entity a claim refers to. Types: Token, Account, Contract, Pool, Transaction, Cohort. |
| Predicate | The property being evaluated. Each predicate has a defined evaluation class (deterministic or inferential) and is independently versioned (Section 2.5). |
| Predicate Version | A semantic version attached to a predicate definition, tracking changes to what the predicate measures. Frozen within an engine version via the Predicate Manifest (Section 2.5). |
| Predicate Manifest | A frozen mapping of predicate IDs to predicate versions within a specific engine version. Ensures replay determinism by making the predicate-engine binding explicit and immutable (Section 2.5). |
| Context | The chain, block range, and temporal bounds under which a claim is evaluated. |
| Scope | Constraints on graph expansion: maximum hops, nodes, edges, temporal lookback. |
| Evidence Unit | A single observation with provenance: source, retrieval method, temporal anchor, and content hash. |
| Evidence Graph | A directed, typed, temporally-anchored multigraph constructed from evidence units for a specific claim evaluation. |
| Verification Object (VO) | The atomic output of Baseline. A content-addressed, immutable record of a single claim evaluation. |
| Qualification | How a claim relates to evidence: VERIFIED, INFERRED, OBSERVED, INCONCLUSIVE, or UNQUALIFIED. |
| Confidence | A structured measure of certainty for inferred results, including point estimate, bounds, and degradation flags. |
| Attestation | A cryptographic signature by a validator confirming that replay of a Verification Object produced an identical result. |
| Validator | An independent actor that attests to verification execution integrity by replaying evaluations. Must meet staking, hardware, and uptime requirements (Section 7.4-7.5). |
| Validator Weight | A composite score reflecting a validator's economic commitment (stake), track record (reputation), and verification capability (archive access). Used to weight attestations for Sybil resistance (Section 7.5.3). |
| Engine Version | A versioned release of the Baseline Verification Engine. Follows semantic versioning. Each engine version includes a frozen Predicate Manifest (Section 2.5, 5.5). |
| Canonicalization | The process of transforming raw evidence into a deterministic, provider-independent representation. |
| BCE | Baseline Canonical Encoding. The deterministic binary encoding specification used for canonicalization. |
| The Line | The boundary between information that can be qualified by verification and information that cannot. |
| LINE | The native token of the Baseline network (rebranded from FirmaChain FCT). Used for staking, fees, and governance. |
| Memecoin Evaluation | A product-level composite score derived from multiple Verification Objects, used by the Memecoin Intel Portal. |
| Ghost Scoring System | The scoring framework (v1 manual, v2 automated) for memecoin fundamental analysis across 12 categories. |
| Feature Engineering | The computation of 26 structured features from raw on-chain events, used by both deterministic and inferential evaluations. |
| Replay | The act of re-executing a verification with the same inputs and engine version to confirm the output. |
| Dispute | A formal contest of a Verification Object's qualification or result, expressed through an alternative evaluation. |
Baseline Technical Specification (Yellow Paper) v0.1 — Draft