Timeline Truth First

HindSite turns completed work into a structured record you can actually trust.

The MVP experience is intentionally calm: ingest, normalize, store, replay, reflect, inspect. Timeline truth leads. AI reflection follows.

Open project workspace Review demo timeline

Current Session

Shipping the deterministic timeline backbone

The working session centers on establishing a trustworthy timeline record before any AI reflection is introduced.

Span: April 16, 2026 · 9:00 AM to 10:00 AM UTC
Canonicalization: v1
Authority: Timeline truth

Backend Workspace

Project and session records live under Workspace.

Use the workspace to create and inspect stored project/session metadata. Those shells organize replay work, but they are not canonical timeline records by themselves.

Demo Surface

This page demonstrates the trust boundary.

The timeline and reflection below are sample presentation data. Timeline truth remains primary; AI reflection stays a secondary commentary layer on stored records.

Canonical Timeline

Shipping the deterministic timeline backbone

The timeline is the source of truth. Each event remains linked to its source evidence and canonicalization version.

commit

Apr 16, 2026, 9:00 AM

Committed deterministic canonicalization groundwork for the replay pipeline.

Source: git

commit abc123
src/HindSite.Api/Canonicalization

pull request

Apr 16, 2026, 10:00 AM

Opened a reviewable change that joined backend truth rules with frontend inspection views.

Source: github

pull request #42
timeline overview endpoint

AI Reflection

Secondary Layer

Reflection, not narration

The AI layer comments on the stored record. It does not create missing steps or redefine what happened.

Themes

deterministic truth

inspectable replay

editorial calm

Guardrails

AI may summarize stored events.
AI may explain canonical sequences.
AI may not invent missing actions, actors, or facts.