Latticra

Home / Claims and evidence

Evidence-Bound Claims

Claims and evidence

Latticra uses exact evidence records to separate concepts, fixtures, tests, reports, guarded experiments, and future real-system claims.

Core Rule

A claim can rise only as far as its evidence.

The evidence ladder prevents design intent from being mistaken for implementation, runtime authority, production security, or operating-system completeness.

Promotion

A capability moves up only when the evidence for the next level exists.

No skipping

A concept cannot jump from simulation or documentation directly to real-device execution.

Demotion

A promoted claim must be narrowed when evidence becomes stale, contradicted, unreproducible, unsafe, or ambiguous.

Evidence Ladder

From concept to supported capability.

The source ladder defines levels L0 through L9. This page groups them for quick public orientation.

L0

Concept

Name, description, diagrams, vocabulary, and non-claims. No implementation or security claim.

L1-L2

Fixture and tested model

Static fixtures, expected output, validation scripts, denied-behavior tests, and explicit non-claims.

L3-L4

Read-only report and preview

Inspectable command surfaces, status labels, invariant tests, failure state, and operator-facing reports.

L5-L6

Guarded local or VM evidence

Narrow opt-in local experiments or controlled virtual targets with logs, validation reports, and reset paths.

L7-L8

Real-device evidence

Read-only or gated real hardware evidence with device identity, operator approval, recovery planning, and post-run validation.

L9

Promoted capability

Repeated evidence, tests, documentation, release notes, support boundary, and safety review.

Claim Language

Use exact labels, not broad promises.

Latticra records should name the evidence level or the narrow status surface. They should not imply production readiness unless that evidence exists.

use

Narrow evidence language

  • L2 tested model
  • L3 read-only command surface
  • L4 runtime preview
  • report-only metadata
avoid

Unsupported broad claims

  • production-ready
  • secure
  • finished operating system
  • real-system execution

Current Posture

Latticra currently stays in low-effect evidence bands.

The public posture centers on contracts, fixtures, tested models, read-only reports, and no-effect local checks. Real-device execution is not claimed.

Supported now

Documentation, contracts, fixtures, no-effect tests, local reports, and public status records.

Guarded lanes

Fedora validation, local RPM work, Panel, Console, macOS planning, and offline AI planning remain status-bound.

Not claimed

Production enforcement, real-device gated execution, root authority, network authority, certification, or OS replacement.

Source Records

Read the exact record before repeating a claim.

These records define the current claim boundary more precisely than a summary page can.

Evidence LadderPromotion levels and demotion rules. Public Claims LedgerAllowed wording, blocked wording, and promotion requirements for public summaries. Product Documentation CohesionProduct-facing reader routes, safe copy rules, and cross-link expectations. ExamplesConcrete local checks tied back to claim boundaries. Kernel and State LatticeCompiled kernel reports, lifecycle evidence, subsystem summaries, and no-external-effect boundaries. Boot preview boundarySeaBIOS/GRUB compatibility, fixture-only evidence, preflight, templates, and blocked bootable OS claims. Runtime boundaryNo-effect runtime records, policy matrix, and blocked operational authority. Seal overviewReport-only evidence and policy-denial boundaries. Latticra PanelGUI workbench evidence, dry-run installer posture, user-local verification, and non-claims. Latticra ConsoleStage-0 operator-base evidence, registry metadata, host contracts, and receipt non-claims. NadiaOffline AI contract lane, Stage-40 metadata, and blocked runtime authority. Security boundariesSafe testing, defensive posture, and non-claims. Supply-chain gatesCI, dependency, SBOM, updater, runtime-authority, release, and production security non-claims. Signed-updater delivery gateClosed update-delivery gate, local-checkout policy, no-effect fixtures, and blocked network self-update authority. Incident response boundaryReporting routes, evidence preservation, response gates, and incident-response non-claims. Vulnerability management gateKEV/NVD review, exception records, release blockers, and product-security non-claims. Cryptographic assuranceFIPS/CMVP gates, key lifecycle, randomness, Seal metadata, and no production crypto claims. Identity and access managementICAM gates, privileged access, MFA planning, credential handling, and no hosted identity claims. Security logging and monitoringEvent-source inventory, audit events, redaction, retention, triage, and no detection-service claims. Backup and recovery resilienceBackup scope, restore testing, recovery prioritization, rollback planning, and no recovery-service claims. Secure configuration and change managementConfiguration inventory, secure baselines, approved changes, rollback planning, drift detection, and no hardening claims. Network exposure and remote accessNetwork inventory, internet exposure, remote access, RMM, DNS/TLS lifecycle, and no network-service claims. Data classification and protectionData inventory, sensitive-data flows, PII review, minimization, retention, disposal, and no customer-data claims. Local validationPanel install evidence, static package lanes, and disposable VM gates. Installer readinessProduction installer gates, local artifact manifest fixture, and release non-claims. Real System ContractIdentity, real-system boundary, and evidence rules. Non-ClaimsUnsupported claims Latticra explicitly does not make. Precursor PromotionRules for moving precursor work into Latticra.