DEVELOPMENT · PUBLIC PRESENTATION LAYER

We built the house. Now we are connecting the research to it.

The current phase is the Public Presentation Layer — the Systems pillar of Loom. The Atlas and public interface are in place; the next work is to surface the trust signals and then move the underlying research artifacts into the public structure.

CURRENT PHASE · PUBLIC PRESENTATION LAYER
01

WHERE WE ARE

The structural shell is complete.

The public Atlas and Hub establish stable routes for cases and research areas. That gives the Flint case and the other pipeline cases a public home without exposing the internal Obsidian/Quartz workspace as the site's information architecture.

Core ontology and governance concepts are represented through the Philosophy / Knowledge / Systems architecture. The EROS area is treated as a research subproject rather than as a replacement for Loom.

Open the complete research record →
03

PHASE 3 · TRUST SIGNALS

The next step is making the system's credibility visible.

Cryptographic provenance infrastructure

Case pages will surface per-object hash and provenance information so readers can inspect the integrity trail behind the research artifacts.

See the provenance work →

Schema implementation and validator hardening

The validator is part of the technical research record. The next presentation step is to expose its validation state through the public interface rather than treating a passing build as invisible infrastructure.

Open the validator source →
04

PHASE 4 · CONTENT INGESTION

Then the research moves into the Atlas.

Flint and the case pipeline

The actual Flint research artifact, followed by the other pipeline cases, will be connected to the stable public Atlas structure rather than exposing internal repository folders.

See the public case index →

Public APIs and verification queues

The systems layer will eventually expose interactive research objects and verification state. The goal is inspectability, not an opaque score or chatbot response.

See the infrastructure record →
05

THE REST OF THE BUILD

What is being built around the trust layer.

06

NOT YET CLAIMED

What Loom is deliberately not pretending is finished.

Not autonomous.

Loom is not being presented as a fully operational autonomous research system.

Not automatically verified.

Automation cannot establish source truth merely because a pipeline completed successfully.

Not independently audited.

The complete research stack has not yet received an independent external audit.

07

BUILDING PRINCIPLE

Specification → implementation → artifact → adversarial test → public description.

A technical feature is not evidence. A validator passing is not proof that a claim is true. The system exists to preserve, test, and expose the research record.

The website is the public presentation layer — not a substitute for the underlying research.