Beta lane · scoped vault folders

SkyeVault Bins are scoped custody folders for work that is bigger than Git.

A Bin is a named folder lane: DevodeRator Bin, SkyeAgents Bin, Client Portal Builds Bin, SupaBoy Build Bin. The point is to protect, export, import, and eventually deploy focused workspaces without forcing them through public Git before they are ready.

What exists now

The repo now includes a beta manifest and local pack command. It can list configured bins, scan files, write a receipt, and prepare a SkyeSecure encrypted pack for a bin so sensitive work can be protected without printing values.

Local commands
  • npm run vault:bins:list
  • npm run vault:bins:export:dry-run
  • npm run vault:agents:export
  • npm run vault:bins:pack -- --bin=devooderator-blog
  • npm run vault:bins:pack -- --bin=skyeagents-bin
  • npm run devooderator:agent:brief
  • npm run devooderator:agent:draft

Agent lane

The DevodeRator Field Scribe now lives in the SkyeAgents Bin. It collects the day's changed files, recent receipts, MCP proof, deploy evidence, and vault state before writing a founder/dev blog in Gray's voice. Autosync can still run the normal repo custody export and then write the companion agent/site bins with dedupe so agent-owned files are not double-written across bin packs.

What stays beta

Import/export/deploy straight from vault bins is the future feature lane. It needs more stress proof before being sold as production. For now, Bins give us the structure, receipts, and encrypted pack path to start using the idea safely.

Security posture

Agents can read bin manifests and receipts. They must not print secrets, passphrases, bearer tokens, private unlock material, or raw env values. Any generated public page should link to gated proof or receipt IDs, not expose private content.