Sentor GitHub

Engineering provenance for the AI era

Git records what changed. Sentor records how and why it changed.

Software moves faster with AI.
Understanding should too.

Every day, developers use AI to create more software than ever before. Git preserves the change—but not the prompts, decisions, validation, or why the code exists.

That’s why we built Sentor.

See the provenance Run the local proof

Local-first · Evidence-aware · Git-native

git log --graph --oneline
  1. provenance snapshot dbb46fb feat: show real Sentor provenance in demo
    Sentor context linked to this commitassociation confirmed
    1 prompt 1 response 3 decisions 4 validations
  2. 523e039Added the complete Sentor workflow as a prominent “A complete local proof” section on the demo website.
  3. 5973096Added copyright wordings
  4. 74d2e95docs: automate GitHub Wiki publishing
  5. 4171dc1build: add Sass and GitHub Pages deployment
  6. edd653aBuild interactive Sentor provenance demo

Git keeps the commit line. Sentor attaches the engineering story.

The missing context

Git shows the diff.
Not the reasoning.

AI can produce code in seconds. But once that code lands, the prompts, tradeoffs, corrections, and validation behind it usually disappear.

Sentor preserves that engineering context as durable, queryable evidence—alongside the code it explains.

GitWhat changeddiff
SentorHow & why it changedprovenance

A continuous engineering record

From intent to evidence.

Sentor records the moments that matter, without pretending correlation is causation.

  1. 01PromptHuman intent
  2. 02DecisionTradeoffs made
  3. 03Code changeFiles modified
  4. 04ValidationChecks performed
  5. 05CommitGit history
  6. 06ProvenanceFull explanation

Evidence remains explicitly classified as Observed, Reported, or Derived.

Interactive real-data demo

Open the story behind a commit.

Explore a captured provenance record from this repository, then see one conclusion derived from its explicitly labelled sources. The inference stays separate from what participants reported and systems observed.

sentor provenance HEAD Provenance verified
COMMIT

Added the complete Sentor workflow as a prominent “A complete local proof” section on the demo website.

523e039 · dodtlim · 19 Jul 2026, 13:35

5files changed+315−2
Show evidence:
Session startedObserved

Objective: Demo

DecisionReported

Feature the complete local proof as a dedicated one-page section

Visitors should be able to reproduce Sentor's intent-to-provenance workflow instead of only viewing a simulated provenance record.

DecisionReported

Place the proof workflow between architecture and benefits

The sequence connects how Sentor works to why provenance matters while preserving the approved single-page narrative.

DecisionReported

Provide copy-all support and disclose workflow side effects

A copyable command block reduces transcription errors, while the file and commit warning makes local changes explicit before the workflow runs.

Derived explanationDerived

The core proof can run without cloud infrastructure

The local-first intent and the observed static workflow together support this conclusion. It remains an inference—not a new observed fact.

ReportedDecision: keep the proof local-first ObservedStatic assets and local Git workflow exist ReportedLocal HTTP smoke validation passed DerivedCloud infrastructure is not required for the core proof
d8df0a51… · derived_from [intent, Git change, validation]
Session endedObserved
aff646b3…
Commit linkedObserved
523e039 · association confirmed

Local-first by design

Evidence in. Explanation out.

Sentor turns engineering activity into a canonical, durable record that can be queried wherever developers work.

CAPTURE SOURCES ›_ CLI sessions✦ AI assistants⌁ Git activity
◉RecorderCollects events
◇Canonical eventsNormalised evidence
⬡Immutable storeContent-addressed
▦SQLite indexFast local query
◎Core queryBuilds provenance
DEVELOPER TOOLS ›_ CLI▣ VS Code

01Local-firstYour engineering record stays close to your code.

02Evidence-awareClaims retain their source and classification.

03Git-nativeProvenance resolves against the commits you already use.

A complete local proof

Record the story.
Then query it.

Run one small change from intent to commit and inspect the provenance Sentor preserves around it.

About one minute · Runs locally

  1. 01
    Capture context

    Start a session, then record the prompt, response, and engineering decision.

  2. 02
    Make and validate the change

    Create a real artefact and attach the validation result as observed evidence.

  3. 03
    Link Git and inspect

    Connect the completed session to its commit, then query the human-readable or JSON record.

Run this in a Git repository. It writes demo.txt and creates a commit.

sentor-demo / local proof 
sentor init

sentor session start "Explain a demo change"

sentor record prompt \
  --text "Add a local demo greeting"

sentor record response \
  --text "Implemented the greeting"

sentor record decision \
  --summary "Keep the proof local-first" \
  --reason "The demo must not require cloud infrastructure"

printf 'Sentor explains this change.\n' > demo.txt

sentor record validation \
  --kind test \
  --command "demo walkthrough" \
  --status passed \
  --artifact demo.txt

sentor session end

git add demo.txt
git commit -m "Demonstrate Sentor provenance"

sentor commit link HEAD

sentor provenance HEAD
sentor provenance HEAD --json

How we built it · 1:55–2:30

The demo is also
the evidence.

Sentor was developed with OpenAI Codex and GPT‑5.6. Product thinking became specifications, specifications became code, and Sentor preserved the engineering story around the commits.

  1. 01 Specified Vision, architecture, milestones Observed
  2. 02 Refined with GPT‑5.6 Product and engineering guidance Reported
  3. 03 Implemented by Codex HTML, SCSS, JavaScript, Actions Reported
  4. 04 Committed with Git Reviewable repository history Observed
  5. 05 Explained by Sentor Prompt, decisions, validation Observed
dodtlim / sentor-demo Open repository

Observed repositorymain

  • ▾sentor-demo-governance-pack
  • ├─ DEMO-DESIGN.md product vision
  • ├─ DEMO-PLAN.md architecture & delivery
  • └─ AGENTS.md engineering guidance
  • ◆index.htmlexperience
  • ◆scss/styles.scssvisual system
  • ◆script.jsinteractions
  • ◆.github/workflowsdelivery

Sentor recording itselfObserved

A linked build story, not a claim.

association confirmed
a41508a
feat: tell Sentor story through Git timelineCaptured linked commit · 19 Jul 2026
1promptReported
1responseReported
4decisionsReported
5validations4 passed · 1 blocked
$sentor provenance a41508a5 changed files

A captured repository snapshot. The current commit is verified separately after every update.

This repository doesn’t just showcase Sentor. Its linked engineering record shows how the experience was specified, implemented, validated, and committed.

Why provenance matters

Build faster. Understand longer.

Explainability

Answer why a change exists without reconstructing intent from the diff.

Maintainability

Give future developers the decisions and constraints behind the implementation.

Developer trust

Keep AI-assisted work reviewable through explicit evidence and validation.

Durable history

Preserve the engineering story as tools, teams, and codebases evolve.

The diff is only half the story

See how your code
came to be.

Start capturing the intent, decisions, and evidence behind every change.

Explore Sentor View this demo
$ sentor provenance HEAD