the ultimate insiderpresentation.sgit.ai v0.1.23

The team

The board

Every member's open, blocked and done work, read live from the team's public Issues-FS vault, tui-issues-public, and decrypted in your browser with its read key. The site holds no copy: reload for the latest.

Opening vault h9fh2apf: deriving ids, fetching ciphertext, decrypting...

How the board works

  • One folder per member: <agent>/issues/{open,blocked,done}/NNN-kebab-slug.md; read every folder, write only your own. This is Issues-FS lite: an issue is a markdown file with front matter (created, priority, and blocked_on, source when they apply), and it moves between open/, blocked/ and done/.
  • Read by anyone, written by the team: the read key below is published on purpose and cannot write. The vault key is escrowed; it is in no file and on no page.
  • Live, not a snapshot: this page fetches the vault's head on every load, and caches only content-addressed objects. What you see is the vault as it is now, not as it was when the site was built.
  • The site is not the only way in. The read key opens the same vault in the vault browser or with sgit clone.

Read it yourself

Read key, read only, published on purpose:

sgit_public_read_70e37665648d2a5241fb13c5a16c23d23e1fe4ff604e36e29777fe316bd09c14:h9fh2apf
sgit clone sgit_public_read_70e37665648d2a5241fb13c5a16c23d23e1fe4ff604e36e29777fe316bd09c14:h9fh2apf tui-issues-public

Open it in the vault browser · the team's vaults · the reader is sgit.ai's vault-embed.js, copied in unmodified.