Spectra andymccall's projects · #7

• Passkey for the owner and the assurance policy: the human's authority out of agents' reach

  ◇ andymccall/spectra#19 · open

  featuresecurity

• The owner's account: sign in with a passkey, over TLS

  ◇ andymccall/spectrahub#7 · open

  featuresecurity

• Register a Spectra and take its uplink: verify every event and checkpoint

  ◇ andymccall/spectrahub#8 · open

  featuresecurity

• Read-only pages: Spectras, channels with replies, agents, briefs, the log

  ◇ andymccall/spectrahub#9 · open

  featureui

• The Constellation

  ◇ andymccall/spectrahub#10 · open

  featureui

• The uplink: spectra serve streams its ledger to a SpectraHub

  ◇ andymccall/spectra#33 · open

  featuresecurity

finished cards are archived after 14 days

• The ledger: SQLite, frozen envelope with hash chain, proofs and HLC, signed checkpoints, verify

  ◇ andymccall/spectra#3 · closed

  feature

• Identities instead of tokens: agents as the owner's Oxygen delegates, signed requests over a Unix socket, ownership shown

  ◇ andymccall/spectra#4 · closed

  featuresecurity

• Projects, presence and sessions

  ◇ andymccall/spectra#5 · closed

  feature

• Channels, threads, messages, inbox and full-text search

  ◇ andymccall/spectra#6 · closed

  feature

• Tuner: MCP over Streamable HTTP (2026-07-28 and 2025-11-25)

  ◇ andymccall/spectra#7 · closed

  featuresecurity

• The 0.1 tools: brief, say, read, inbox, wait with the idle guard, search and the rest

  ◇ andymccall/spectra#8 · closed

  feature

• The stdio shim: spectra mcp --agent NAME, signing with the agent's key

  ◇ andymccall/spectra#9 · closed

  feature

• Radar: Live, Channels, thread and Log pages with owner sign-in and live updates

  ◇ andymccall/spectra#10 · closed

  featureui

• JSON API for 0.1 and spectra-api types with make ts

  ◇ andymccall/spectra#11 · closed

  feature

• Human CLI: spectra say, inbox --follow and search

  ◇ andymccall/spectra#12 · closed

  feature

• Server over TLS: a certificate signed by the instance key, /api/v1/instance, no uid over TCP

  ◇ andymccall/spectra#20 · closed

  featuresecurity

• Remote setup: spectra init --owner KEYID and the owner's claim from the client

  ◇ andymccall/spectra#22 · closed

  featuresecurity

• spectra connect and the TLS client: trust through the owner's delegation, pinned certificate, shims over the network

  ◇ andymccall/spectra#21 · closed

  featuresecurity

• The CLI without a ledger file: every command through the JSON API

  ◇ andymccall/spectra#23 · closed

  feature

• Radar from a workstation: spectra open's loopback proxy to the pinned server

  ◇ andymccall/spectra#24 · closed

  featureui

• Own identities, signatures and CBOR: Spectra uses Oxygen in no way

  ◇ andymccall/spectra#26 · closed

  featuresecurity

• A project is any kind of work: an optional folder Spectra never reads, links drawn by the owner

  ◇ andymccall/spectra#27 · closed

  feature

• Briefs: an overall brief and one per project, signed in the ledger and delivered to agents

  ◇ andymccall/spectra#29 · closed

  feature

• Radar Constellation: the live picture of projects, agents and messages

  ◇ andymccall/spectra#30 · closed

  featureui

• spectra bridge and spectra probe: sign for the editor, set up without the command line

  ◇ andymccall/spectra#31 · closed

  featuresecurity

• 0.1 Just works: setup walkthrough, bridge, chat, briefs

  ◇ andymccall/spectra-vscode#6 · closed

  feature