Skip to content

Remote Control: brainstorm then spec (after Phase-2 auth lands) #57

Description

@adbarc92

Step 4 of the build order, and a future pillar of the north star: drive the fleet away-from-desk.

Needs its own brainstorm → spec cycle, after Phase-2 auth lands (#55).

Do not start the transport design early

fleetd is currently an unauthenticated loopback daemon with ambient push credentials. Phase 2 settles the auth model in code (router-level loopback auth + token handshake on every mutating endpoint). Speccing Remote Control's transport before that model exists means designing against assumptions that Phase 2 will invalidate.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions