DreamLake
  1. DreamLake
  2. Notes
  3. Lakeshore
  4. ML-Dash
  5. CLI

Dev Notes

Development notes record what changed, what was tested, and what remains. Draft implementation, merged code, a release and verified deployment are separate states.

  • Tabbed views and artifact viewer API — proposed layout-owned tabs, view identities and TypeScript examples; click wiring deferred.
  • Linked Notes — list extraction, raw references and full-height side panels.
  • Vault CLI/Python reference audit — corrected HOTP usage, native PTY coverage and transport-retry limits.
  • Remote Vault delivery — private-run delivery, published clients, staging readiness and remaining hosted acceptance.
  • Vault runtime — main API startup wiring and activation status.
  • Vault import — selected SSH imports and pass OTP preview in CLI and Python.
  • Provider execution — proposed declarations, associations and tracked-run integration; no scheduler delivery yet.
  • Host enrollment — deployed enrollment, signed callbacks and remote command verification.
  • SSH through nymph — native SSH behind NAT; admission and framing are implemented in a draft PR.
  • Queue mounts — staging deployment, API acceptance and remaining client/UI delivery.
  • Elastic queues — queue delivery, large results, restart acceptance and remaining provider integration.
  • Compose capacity — merged count convergence and local recovery safeguards; release/deployment unverified.
  • Nymph supervisor identity — local ownership and verify-before-kill; released in nymph v0.1.5; verified artifacts, test instructions and remaining host acceptance.
  • Tasks — task folders, progress events, reusable skill and dated deployment receipts.
  • Environments — namespace environment collections and sim playback: DreamDB storage, dreamlake env CLI, MuJoCo/URDF viewers and dataset playback views; deployed to staging and production, docs live; the CLI npm channel and the viz view reference remain open.
  • Release notes — unreleased changes and, when available, shipped versions.
  • Master plan — coordination and workstream status.

Each active workstream should add a topic here, maintain dated entries and update release notes. After every dev-note update, send Ge a Slack DM with the note link, change summary and validation/delivery status. Use a source link until the page is deployed. See the repository's docs/DEV_NOTES.md for the task and memo convention.

  • Prefix KMS — trusted empty-prefix activation, recovery and remaining migration work.