The project board that writes itself.

Your coding agents fill in the board as they work. Nobody moves a card.

Your engineers' coding agents fill in the board as they work. You read it each morning and reply from the same page. Nobody moves a card.

Every board is also a record. When you need to prove it, turn the Ledger on.

See how it works

attestia.dev/demo

Team board

Data from the last deploy

25 Oct 2026

Filled in from each engineer's coding sessions. Each day closes at midnight New York.

104.7

Hours · all time

193

Tasks done · all time

753

Commits · all time

In progress · stories

Latest day

25 Oct 2026

Aatir

Owner and engineer

0.8 hestimated

Aatir recorded no timed session and made 1 commit. No task moved; the commits were about day end 2026-10-24 (aatir). Nothing is blocked. Next: (1) Keys the program holds, part B first step: tracker/keys/ and the allowed signers in the chain; CUI marking; FIPS pinning (The record and the Ledger) (2) Session end mini seal: a signed hash of the files the hook wrote, chained forward; the close chains the day's seals (The record and the Ledger) and 1 more.

Technical details · 1 commit

No session had a clock on this day, so the hours are the union of 45 minute windows ending at each commit.

Chained and anchored outside the repository at the close.

Commits

95a2c2c

Stored in your GitHub repository. All times are New York.

Live: this is Attestia's own board. Open it full size

Boards assume someone updates the card.

With coding agents, the work happens while nobody is watching.

So the board goes stale, and you go back to asking.

Three moments, no typing.

A session opens: the agent sees yesterday, today, and anything you assigned.
It records as it works, in the same commit as the code.
At five past midnight the day closes itself, signed and pushed.

Three moments, no typing.

session opens

Day start

Opening a session starts the day. The agent sees yesterday, today's plan, and anything you assigned.

Example

Day start for Alex, 2026-09-11 (Eastern). Created tracker/log/2026-09-11/alex.json.Last shipped: 2026-09-10: Done: Month picker; 4 commits (4 commits)Blocked: noneToday: Continue 012-billing-exports: CSV emitter | Start 012-billing-exports: PDF bundleAssigned to you on the board: 1 open task (#41 Add a search box to the invoice list). Open change requests: 0.Record task status in tracker/stories/ as you work. The day closes automatically at 00:05 Eastern; say "day end" to close early.

session works
Record as you go
Every task the session starts, blocks, or finishes is written to the repository in the same commit as the code. Hours come from the session's own clock.
Example
Billing exports
3 of 6 done. Working on: PDF bundle.
In progress
In progress
PDF bundle
Blocked
None
To do
Email the file when it is ready
Close
Done (3)
midnight
The day closes itself
At five past midnight the day is finalized for everyone, signed, pushed, and the board is current before you open it.
Example
Alex
Engineer
5 h
3 updates across 1 story, 3 commits, 5 hours.
Billing exports
Done: CSV emitter
Started: PDF bundle
3 commits: feat(exports): CSV emitter; feat(exports): PDF bundle scaffolding
3 commits
Next
- 012-billing-exports: PDF bundle
Technical details
Intervals
11 Sept 2026 09:02 11:40
11 Sept 2026 10:10 14:02
Commits
d161ee2
9c4b0aa
3e8f1c0

Open one page each morning.

attestia.dev/demo#phases

10 phases. 2 done, Foundation is nearly done.

76%

Each phase counts the tasks of its stories; the total is the average of the phases.

1Foundation98%In progress

Before any product code: the written spec is settled, the app skeleton exists, and the board's own record keeping runs on this repository so the build is visible from day one.

Settle the written spec
Shipped
Repository foundation
Shipped
Marketing site
In progress

2The board100%Shipped

What a product owner opens: today's work by person, the build by phase, every feature and its tasks, the daily log, and a link that can be shared without a login.

The board
Shipped

3Sign in, tasks, and Ask88%In progress

Members sign in by email, hand out work and answer decisions from the board, and ask questions that get answered from the repository.

Sign in and the GitHub App
Shipped
Tasks as issues
In progress
Ask the repository
In progress

4Install and ship83%In progress

A new team gets running in minutes, and the first outside customer migrates onto the hosted product.

The CLI: init and install
In progress
Deploy and the first team handoff
In progress

5Assistants and onboarding100%Shipped

Two things that make the product usable beyond this team: a connector so an assistant outside the repository can ask where the build is, and an onboarding path where the board proposes the team from git, seeds itself from history, and shows a checklist until the first real day.

MCP server
Shipped
Onboarding
Shipped

6The record and the Ledger77%In progress

Every session records which agent and model did the work, every agent authored commit carries a named human review, the nightly close signs and chains the record and anchors it outside the repository, and a verify command lets an assessor check it offline. Cost, quality, and policy views read the same files.

The record and the Ledger
In progress
The site, enterprise first
Shipped

7The federal pilot62%In progress

A delivery team on a federal program installs the tool from one archive without the internet, keeps the record for a month, and hands its assessor an evidence package with a packet that speaks in control language. The assessor's written answer is the proof point.

The federal pilot kit
In progress
The documentation package
In progress
Packaging and state
In progress
The pilot archive
In progress
The diagrams
In progress

8The rebrand65%In progress

The name changes on everything a customer sees, in one deploy, after the domains, the trademark filing, and the clearance opinion are in hand. The record, its folder, its fields, and every anchored day stay exactly as they are; old commands and links keep working for a year.

The rebrand: Attestia
In progress
Search: the new domain and name
In progress

9Go to market10%In progress

A security lead finds the site by searching the rule they were handed, believes one page, verifies it in their browser, sees a price, and can name a firm they already work with that uses it. Planned, not started.

The go to market kit
In progress
Self service purchase
Planned

10Release and support75%In progress

A customer's engineer can say what they are running, prove it came from us, rebuild it and get the same result, read what changed, and reach a person. Needed before the first outside team, and ahead of the cloud templates in the build order. Planned, not started.

Release and support
In progress

Done

The site leads with the rule that took effect on September 8: the amended home page, the Ledger page's rule section, and the owner's verified quotations.
The product name is read from one place per surface, so the rename flips a variable and nothing is find and replaced.
A self hosted anchor for programs that cannot reach a public log, and a signer the install fetches and verifies or takes from the machine's own key.
The self hosted board as a container image with a four line setup for GitHub Enterprise Server and GitLab, and the command line tool as a checksummed, signed tarball that installs offline.
A receipt per commit to paste into a pull request, and blame from a file to the session, model, director, and reviewer that touched it.
The new name is live at its own domain, with the old site untouched, ahead of the copy and board work that follows.
Search engines and link previews see the new domain properly: one list of public pages behind the sitemap, private surfaces kept out, and every page carrying its own address and title when shared.
The pictures: where the boundary falls and what crosses it, what holds what, how a record is written, and how a stranger with no network checks it.
The product's own verify passes on a clean copy, as an assessor runs it; the one day recorded wrongly is corrected in the open, and verify proves the correction.

Now

A new name, going live at its own domain on the owner's call: a second deployment carries the new brand while the current site stays as it is; the pages, emails, and demo follow.

The owner's search console steps for the new domain: change of address once the old domain redirects, the www redirect made permanent, the sitemap submitted once.
The federal pilot kit: the default policy, the one page guide, the assessor packet, the security answers, the agreement, and the archive.
The owner's dry run of the kit on a clean machine with the network off, then the pilot record.
The first outside team's first week.
The go to market kit is planned: two guides on the rule and on agent provenance evidence, a trust page, a price on the page, and a partners page, in that order.
One file a program copies inside its boundary: the images, the tool, the compose file, the policy, and the documents, with a one page guide from the archive to a verified record and no internet.

The Phases tab, live. The hero above is the Today tab.

Today. One card per person. What moved, what is blocked, hours with the intervals behind them.
Phases. The whole build as one bar. Click a phase for the features inside, in plain words.
Stories. One row per feature. Progress, what is being worked on, who owns it.
People. Every person's page. Their tasks, their features, their hours.

Talk back from the board.

Pin a note on the live product

Coming next

Circle the thing that is wrong. It becomes a task with a screenshot, on the right page, for the right person.

Example

/portalPinCircleArrow

Approve deliverable

The approve button is easy to miss. Make it the main action on this page.

Saves a screenshot and becomes a task

Save note

Ask the repository

Ask about the build. An agent reads the code and answers in minutes, without pulling in an engineer.

Example

Ask the repository

Is the client portal ready for the Hartwell demo on Friday? (example)

Nearly. Clients can sign in, see open work, and approve a deliverable as of today. Two things are not ready: comments on a deliverable are still to do, and storing signed approvals is blocked on a decision that is waiting for Maya. If that decision lands tomorrow, the demo can show the full approval flow.

Example answer, in about 3 minutes

Answer decisions in one click

When the team needs a call, you get a card with a recommendation. Agree in one tap, or write your own.

Example

Decide: where signed approvals are stored

Where should a signed approval be stored?
Recommended: In our own database, with a copy of the PDF in object storage. Simplest to audit.
AgreeSomething else
Should clients be able to download their signed approvals?
Recommended: Yes, from the portal, as a PDF with the signature block.
AgreeSomething else

1 of 2 answered. You can send some now and the rest later.Send

Hand out work

Assign a task to a person. Their next coding session picks it up as the day's work.

Example

Give someone a task

Add a search box to the invoice list

Alex

Due 18 Sept 2026

Assign a task

Next morning in Alex's session: Assigned to you on the board: 1 open task

Hours you can defend.

Every hour is a timed interval from a real session, not a guess from commit times.

Engineers control their own clock.

Any correction is signed.

Example

Alex

Engineer

5 h

3 updates across 1 story, 3 commits, 5 hours.

Billing exports

Done: CSV emitter
Started: PDF bundle
3 commits: feat(exports): CSV emitter; feat(exports): PDF bundle scaffolding

3 commits

012-billing-exports: PDF bundle

Technical details

Intervals

11 Sept 2026	09:02	11:40
11 Sept 2026	10:10	14:02

Commits

d161ee2
9c4b0aa
3e8f1c0

Teams that do not bill by the hour turn hours off with one setting.

Who it is for

Founders: the morning record replaces the standup.
Agencies: your client reads the build and signs off on hours.
Teams on git native trackers: give the rest of the company a page.

Built for the people who asked for the software.

Founders with a small team

The morning record replaces the standup. Ask replaces the interruption.

Agencies and studios

Your client is the product owner. They see the daily record, leave notes on the live build, and sign off on hours without a status email.

Teams already on git native trackers

Keep how your engineers work. Give the rest of the company a page.

$ npx @attestia-dev/cli init$ npx @attestia-dev/cli installDay start for Alex, 2026-09-11 (Eastern). Created tracker/log/2026-09-11/alex.json.Last shipped: 2026-09-10: Done: Month picker; 4 commits (4 commits)Blocked: noneToday: Continue 012-billing-exports: CSV emitter | Start 012-billing-exports: PDF bundleAssigned to you on the board: 1 open task (#41 Add a search box to the invoice list). Open change requests: 0.Record task status in tracker/stories/ as you work. The day closes automatically at 00:05 Eastern; say "day end" to close early.

For engineers

One command in the repo, one on your machine. Status is written as JSON in the same commit as the code, signed, with git as the audit trail. You never type it again.

Works with Claude Code today. More runtimes coming.

Free during early access

One repository, up to three people, free.

The CLI, the hosted board, tasks, Ask through your own workflow, and the record with identity and review. The Ledger, Team, and Enterprise tiers are on the home page.

Get early access See all pricing

The project board that writes itself.

25 Oct 2026

Latest day

Three moments, no typing.

Three moments, no typing.

Day start

Record as you go

The day closes itself

Open one page each morning.

Talk back from the board.

Pin a note on the live product

Ask the repository

Answer decisions in one click

Hand out work

Hours you can defend.

Who it is for

Built for the people who asked for the software.

Founders with a small team

Agencies and studios

Teams already on git native trackers

For engineers

One repository, up to three people, free.

See what your build actually did today.