Skip to content

[Release gate] Mobile connection flow v1: the maintainer closes this card to release its cards for dispatch #150

Closed

Description

@hotlong

This card exists only as a dispatch gate. The maintainer asked for the cards of the mobile connection-flow design to be filed but not dispatched yet, verbatim:

「开卡,不要派发」

Every card of the design carries Blocked-by: pointing here: the mobile cards, plus the objectstack-ai/objectstack and objectstack-ai/cloud cards (which also carry pm:blocked). Closing this card releases them through the ordinary unlock scan. No seat closes it; the maintainer does.

The design

The design is a canvas, "ObjectOS Mobile — screens and connection flow" (private to the maintainer until shared). It covers three entry paths that all land in one Console:

  • ObjectOS Cloud: sign in once at cloud.objectos.ai → choose an organization → hand off to that organization's single production environment. Development environments are not shown on mobile. The environment model itself is open in objectstack-ai/cloud#3487, and every option there keeps one production environment per organization.
  • Private deployment: scan a QR code, type an address, or follow an invite link → an anonymous probe (/.well-known/objectstack, /api/v1/runtime/config, /api/v1/auth/config) → a confirmation screen with the server's branding → the Console sign-in page.
  • Managed (MDM / white-label): a server URL delivered by managed app configuration, optionally locked.

Shared rules:

  • The shell holds no API credential; sessions stay in the WebView, isolated per organization or server.
  • Navigation admits only the current server, *.objectos.ai in Cloud mode, and the identity provider during a sign-in.
  • The Console registers the push token after sign-in.
  • The brand is ObjectOS throughout; bundle id ai.objectos.mobile (maintainer, 2026-11-02, verbatim: 「包名用 ai.objectos.mobile」).

Cards behind this gate

Listed in a comment below once filed.

Activity

  1. hotlong commented on Nov 2, 2026

    @hotlong
    ContributorAuthor

    Cards behind this gate

    Every card below carries Blocked-by: objectstack-ai/mobile#150. The objectstack and cloud cards also carry pm:blocked, so their standing triage seats skip them until this card closes.

    objectstack-ai/mobile (the repo:mobile seat, summoned on demand)

    Card What Depends on
    #151 Rebrand to ObjectOS: app name, scheme objectos, bundle id / package ai.objectos.mobile — (do first)
    #154 Private servers: probe with the anonymous discovery endpoints, then a confirm screen —
    #152 Saved connections and the native 切换组织 switcher —
    #156 Connect by QR code (objectos://connect?server=…) and the native scanner #151, #154
    #153 Cloud mode: sign in at cloud.objectos.ai, pick an organization, land in its environment #152, objectstack-ai/cloud#3489
    #155 External sign-in bar for enterprise IdPs (security boundary; maintainer merges) #152
    #157 MDM managed app configuration (serverUrl, lockServer) #152, #154
    #158 Repo docs: AGENTS.md / CLAUDE.md, ROADMAP as direction plus links, HYBRID-SHELL connection model the cards above, as they land

    objectstack-ai/objectstack

    objectstack-ai/cloud

    Already filed, not behind this gate

    These belong to the same design:


    Generated by Claude Code

  2. hotlong commented on Nov 2, 2026

    @hotlong
    ContributorAuthor

    One more card behind this gate:


    Generated by Claude Code

  3. objectstack-fleet commented on Nov 2, 2026

    @objectstack-fleet
    Contributor

    repo:mobile#1 · os-justin · session_01QSeKYnW1Xf6HDSWz1eGAqv

    Gate released 2026-11-02T12:04Z — closed by the repo:mobile seat on the maintainer's instruction.

    This card says no seat closes it. The maintainer overrode that for this one close:

    • Who: the maintainer (Justin), the account this seat runs under.
    • Verbatim: 「开始派发 mobile 车道」, then, asked whether that releases this gate, chose 「放行,席位代关 (Recommended)」.
    • Where: the Claude Code session session_01QSeKYnW1Xf6HDSWz1eGAqv that summoned this seat, 2026-11-02.

    What happens to the cards behind it (each card gets its own state and comment):


    Generated by Claude Code

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions