LABSPUBLIC RESEARCH INSTITUTE
← Benchmark centerVERSIONED EVIDENCE CONTRACT

FOVEA Correctness and Cognition

No public result exists merely because this contract exists. It defines what must be run, recorded, and disclosed before a result can be promoted.

Read related paper
REQUIRED SUITES
  1. Address golden vectors
  2. Parent/child/neighbor property tests
  3. Hilbert encode/decode and locality
  4. LOOK determinism and restore
  5. Atlas deletion and reconstruction
  6. Proof-breach rendering
  7. Bytes/tokens moved versus competent lazy loading
  8. Landmarked field versus plain grid versus search
INVALID-RUN CONDITIONS
  • incorrect address arithmetic
  • address churn
  • trusted unfold without receipt
  • projection cache treated as truth
  • unreceipted benchmark configuration
METRICS
exactnessreconstruction agreementbytes_movedtokens_movedtime_to_refindnavigation_errorsperipheral_cue_useuser_preference
EXAMPLE RECEIPT · NOT MEASURED
{
  "run_id": "b01-fovea-correctness-cognition-example-NOT-MEASURED",
  "suite_id": "b01-fovea-correctness-cognition",
  "suite_version": "1.0.0",
  "commit": "UNSET",
  "configuration_digest": "UNSET",
  "corpus_or_task_digest": "UNSET",
  "model_and_runtime": {},
  "environment_digest": "UNSET",
  "started_at": null,
  "finished_at": null,
  "raw_artifact_refs": [],
  "metric_records": [],
  "invalid_conditions_checked": [],
  "known_limitations": [
    "Example only; no measured values."
  ],
  "result_state": "AWAITING_LOCAL_RUN",
  "receipt_digest": "UNSET",
  "example_only": true
}
CI FIXTURE RECEIPTDETERMINISTIC FIXTURE CONFORMANCE

Contract structure and example-receipt invariants only. No metric was measured and no benchmark result was promoted.

{
  "checks": {
    "example_cannot_be_measured": true,
    "invalid_conditions_declared": true,
    "metrics_declared": true,
    "receipt_contract_complete": true,
    "receipt_suite_matches": true,
    "related_paper_present": true,
    "required_suites_declared": true,
    "suite_id_matches_directory": true,
    "suite_version_present": true
  },
  "contract_sha256": "ce4cf35034e5c8d7af55ff25084951253a3caa94cc17fe606b483fbcd6af8a87",
  "measured_metrics": false,
  "note": "This receipt validates the benchmark contract fixture only. It is not a benchmark run and contains no performance or comparative result.",
  "performance_result": false,
  "result_state": "DETERMINISTIC_FIXTURE_CONFORMANCE",
  "suite_id": "b01-fovea-correctness-cognition",
  "suite_version": "1.0.0"
}
FOUNDER-LOCAL RUN PACKETS

These one-command packets fail closed when hardware, source, model, dataset, participant consent, or checkpoint prerequisites are absent.

FOVEA-LANDMARK-MEMORY-AB · AWAITING_LOCAL_RUN ↓FOVEA-RUST-CONFORMANCE · AWAITING_LOCAL_RUN ↓
RELATED IMPORTED EVIDENCE

These records retain their own scope and limitations. They do not cause every suite in this broader contract to pass.

E-FOVEA-PROOF-DECK-AUDITVERIFIED MECHANISM

GlyphDrive/FOVEA proof-deck independent verification

Reproduced 12/12 shipped self-tests and responsive/browser checks; independent audit also found open proof and security defects.

  • Green fold verification was self-hashed rather than checked against a pinned receipt.
  • Same-frame restore was not actually proven.
  • Long address arithmetic and unescaped input were release blockers in the audited deck.
independent-verification.md →
E-FOVEA-OOC-ASSESSMENTSOURCE REVIEWED

GlyphDrive/FOVEA/OOC technical assessment

Technical assessment and v0.2 research plan supporting narrow mechanism claims and explicit future gates.

  • Founder-local Rust conformance, full codec baselines, and cognition experiments remain unrun.

Objective

Establish a reproducible, falsifiable evidence path for p03-fovea-address-fabric. This contract authorizes no result by itself. A public result requires a versioned run, exact configuration, raw artifacts, environment identity, limitations, and a receipt.

Required suites

  1. Address golden vectors
  2. Parent/child/neighbor property tests
  3. Hilbert encode/decode and locality
  4. LOOK determinism and restore
  5. Atlas deletion and reconstruction
  6. Proof-breach rendering
  7. Bytes/tokens moved versus competent lazy loading
  8. Landmarked field versus plain grid versus search

Invalid-run conditions

A run is invalid, rather than merely low-scoring, when any of the following occurs:

  • incorrect address arithmetic
  • address churn
  • trusted unfold without receipt
  • projection cache treated as truth
  • unreceipted benchmark configuration

Metrics

Report each metric separately. Do not hide a regression inside one composite score.

  • exactness
  • reconstruction agreement
  • bytes_moved
  • tokens_moved
  • time_to_refind
  • navigation_errors
  • peripheral_cue_use
  • user_preference

Baseline discipline

Use the strongest sensible baseline for the exact task and information budget. Pin versions, prompts, corpora, models, hardware, runtime flags, and warm/cold state. If the research system receives additional context, dependencies, precomputation, or a model, charge or disclose them under the contract.

Run receipt

Every run emits:

run_id
suite_id
suite_version
commit
configuration_digest
corpus_or_task_digest
model_and_runtime
environment_digest
started_at
finished_at
raw_artifact_refs[]
metric_records[]
invalid_conditions_checked[]
known_limitations[]
result_state
receipt_digest

Allowed result states:

REPRODUCED
VERIFIED_MECHANISM
IMPLEMENTED
SOURCE_REVIEWED
SPECIFIED
HYPOTHESIS
INCONCLUSIVE
FAILED
AWAITING_LOCAL_RUN
INVALID

Data splits and leakage

Freeze task sets before viewing final results. Keep development, selection, and held-out evaluation separate where the suite supports them. Record any human-authored fixture that appeared during implementation. Do not tune a threshold on the final set and present it as held out.

Statistical and qualitative reporting

For repeated measurements, report sample count, central tendency, dispersion, and uncertainty appropriate to the design. Preserve row-level results. For human ratings, blind condition labels where possible, record the rubric, and retain disagreement rather than averaging away failure modes.

Negative evidence

Failed and inconclusive runs remain in the experiment ledger with code, configuration, and reason. A later successful run does not delete them.

Publication requirements

A public result page must show:

  • exact evidence state;
  • date and commit;
  • environment and task/corpus identity;
  • metric table;
  • baseline table;
  • raw artifact links;
  • failure gallery;
  • limitations and non-claims;
  • reproduction command;
  • receipt digest.

No marketing page may round a measured result into a broader claim than the contract supports.