Files
archie/prompts/organisation-automation/04-navigation-and-setup.md
T
2026-11-17 17:53:58 +11:00

3.3 KiB

Implement navigation and contextual setup from working contracts

Read 00-start-here.md and GUIDELINES.md. Work against archie-core-3z4fd.1. Verify its connection and ownership prerequisites before starting. The old page-rearrangement proposal is rejected, not a UI specification.

Outcome

The visible application reflects actual resource ownership. An operator can find and complete the setup needed for a particular workflow and recover a failed run without guessing which settings page owns the problem.

Required behaviour

  1. An organisation selector establishes context. Workflows, Tasks, Connections and Organisation settings operate in that context. Switching org must clear or refetch scoped state and prevent stale responses from contaminating it.
  2. Instance administration is a separate administrator destination for infrastructure and instance limits. Personal login security, API tokens and preferences live in the account menu. Do not recreate a catch-all Access page.
  3. Connections are discoverable organisation resources. A repository opens its connection; a workflow shows the execution identity/resources it needs; a failed task links to an authorised recovery action. Show names with stable references, without duplicate organisation labels or unexplained internal IDs.
  4. Setup is contextual. A repo-required workflow offers missing connection, repository, identity or model configuration where needed. A repository-free workflow never demands GitHub. Chat channels and a global default model are not universal setup prerequisites. Do not add a mandatory global wizard.
  5. Readiness comes from backend capability diagnostics for the selected org, identity, workflow and resource. Distinguish saved/applied/verified/failed. Do not infer readiness from nonempty fields, task counts or a resolved secret.
  6. Recovery consumes structured service errors. The browser must not classify root causes using error-string patterns or display actions the user cannot perform. Preserve task context when moving to configuration and returning.
  7. Preserve the prior working settings draft/save flow, readable width, review diffs, workflow validation and truthful loading/error states. Do not reintroduce native navigation prompts that discard drafts or collisions with the chat FAB.
  8. Keep technical implementation details out of normal product copy. Explain connection/account/permission problems in terms useful to the operator, not daemon config keys, NATS subjects or secret plumbing.

Acceptance evidence

Drive the real local UI: create or select an org, configure the private-repository connection, choose a valid execution identity, verify repository access, start a workflow, encounter and recover a controlled access failure, then retry. Also run repository-free automation without forge setup. Verify a second org cannot see or select the first org's resources, including after switching org during an in-flight fetch. Check administrator, ordinary member and personal account views, loading/error states, keyboard access and a narrow viewport. Capture evidence, regenerate embedded UI output and run the exact final tree's project gate.

Do not claim a successful user journey based solely on mocked screenshots or fixture state. Leave unmet criteria explicitly open in the issue.