The execution ledger for autonomous coding agents
Verification — not human review — is the merge gate. Every change carries signed provenance, machine-checkable intent, and evidence. This hub has no repository yet.
Create a repository
Your browser key becomes the authority root. Delegate roles, set policy, approve landings — every action signed in-page.
generate an identity key in Access first
Bridge an existing GitHub repo
Import a git HEAD through the gate; agents land certified work; export conventional commits back — GitHub keeps its front door.
runs the weft CLI against this hub — see the Git bridge tab after import
Overview
certified landings, live from the gatePending approvals
action neededCertified landing log
Rejections
gate refusedIntents
the work graph — what should happen, machine-readableCreate intent
All intents
Files
head workspace · seq –Tree
Select a file
Access
identity & capability graph — roles are minting templates, never database rowsYour identity
Delegate a role
Capability graph
Policy
the machine-enforceable merge gateActive policy
Git bridge
GitHub keeps its front door — Weft is the agent-side execution layerUpstream
not bridgedExport landed history
Writes every certified landing as conventional git commits — chained onto the original base commit, with Weft-Change / Weft-Model / Weft-Author-Key trailers. Byte-deterministic: re-export produces the identical sha.
then git log weft-export · commits count: 0
Bridge a repo into this hub
the import itself lands through the gate — no side doors. v1 imports the HEAD tree (text files); full-history import is on the roadmap.