The investors page has the architecture, the traction and the business model, and a dashed box where the ask goes. Round size, instrument and the use-of-funds split are the author's to state; nothing is invented in the meantime. Unblocks: a page that can be handed to an angel without a caveat.
The board
The open work on this site, as a kanban. Each card is a markdown file in a vault of its own with a status line; the columns are those lines, rendered. Needs are items only the author can supply and are kept visible rather than discovered late; everything else is work an agent can pick up from its starting prompt.
The vault is the truth; this page is a snapshot. The board lives in vault
pdulwi6i and is updated by sgit push with no site release. What you see below is the state at site v0.2.64, rendered from a clone the release pulled first. For the live board, open the vault — the read key is the whole credential, because every card is public:f41d03b0de550479b3c4359709130386df48f34b2cd75e5ed83de28e9776b479:pdulwi6iOpen the live board in a new tab ↗Five columns from the same files, as the vault holds them right now.
17 items — 14 open, 6 of them waiting on the author. Each card is a file under admin/content/team/issues/; moving a card is editing its status line.
Needs — only the author can supply 6
Your other companies publish the pitch in the open (investor.myfeeds.ai). Either the sgit deck exists and should be linked, or the investors page is the source and a deck can be built from it — a vault with a presenter app, like the VoiceDebrief pitch. Unblocks: something to show in the room next week.
The homepage's strongest multi-agent claim — a branch per agent, a human reviews the merge — has no published vault behind it. If one exists, its read key is enough; if not, the next multi-agent build should be run so its history shows it. Unblocks: closing the gap the after article names; it goes in the hero.
The other agent's fix is {"permissions": {"append": {"write": true}}} and a switch to sg.append.write — not network: true. When it lands, the page's status note comes off and the two 'nothing sent' footers should be gone. Unblocks: the games vault page describing behaviour the vault performs.
Sent to the SG/API team on 7 September (in the CLI repo under team/humans/dinis_cruz/claude-code-web/09/07/). The two that matter most: which hosts serve /api/vault/append/*, and whether the enum-key derivation is stable enough to publish as a spec. Unblocks: the API page stating facts where it currently says unresolved.
bite-coil (a live provider key in key.json, since rotated) and 6kdhnpfx are held on audit findings. Both are republishable via a fresh vault with the offending file removed. A decision either way closes them. Unblocks: the vaults count telling the whole story.
Backlog 6
Agreed direction: who builds it (one human and the roles on this page), why, the commercial line (sgraph.ai sells the hosted service; the code stays Apache-2.0), and two sections borrowed from open-source.sgit.ai/about — Interests declared and Reach me, or correct me — with a !site card out to the fuller record rather than a copy of it.
The earlier 24-key sweep used the presence of .sg_vault/ as success, which an all-zeros key also produces. Three vaults were verified properly by decrypting content; the other 21 were not. Re-run with clone_mode.json as the marker and a negative control.
The pane (assets/site-chat.js) has three tiers and the third is not wired: when a page renders inside a vault, sg.llm.chat would let the host hold the key below the permission floor. Blocked on one fact — whether the bridge's chat contract accepts OpenAI-style tools and returns tool_calls. Ask llms.sgit.ai's owners; until then the pane falls back to the key-in-page tier with the warning it already carries.
The page should print to one or two clean pages for the event. The site already has @media print rules; extend them for the investor bands and check the output.
DNS and a repository exist; the site 404s from GitHub Pages. Listed in the network directory as not published yet rather than omitted. Re-check weekly.
The site is at sg-sentinel.sgit.ai; the sg- prefix is load-bearing. Noted on our graphs page since 21 August; the brief to their team is the remaining step.
Doing 0
empty
Review 2
Nine roles as files under admin/content/team/roles/, a page each; the starting prompts for the regular tasks; this board, as files under admin/content/team/issues/. In review: does each prompt start a fresh agent correctly with nothing but the page?
Same structure as investor.myfeeds.ai — hook, how it works, architecture, market, traction, business model, the ask, use of funds — with the traction numbers computed from the site and the ask left visibly open (N1). In review: nothing on it may be a number the author has not supplied.
Done 3
Shipped as v0.2.57 and v0.2.58: generated from vaults.json, # as a permanent publication ordinal, published dates from git.
Shipped in v0.2.59. One line in markdown; the card pulls the target site's own category and thesis from sites/*.md.
Moving a card is editing one line in the vault and pushing; the site picks it up at its next release. Adding one is adding one file with
id, title, kind (need | task), status, role, priority, opened and a body that says what it unblocks, then python3 tools/reindex.py so the app can read it outside a host. A card that names a Need is closed only by the author's answer. Corrections to published claims are not cards; they are version-log entries, so the record of the mistake is never tidied away.