Files
archie/prompts/organisation-automation/00-start-here.md
T
sam ec9bf5feb2 docs: track work in Gitea issues instead of beads
Every one of the 1709 tracker issues was created in Gitea and checked field by
field against its source record: title, body, state, label set, assignee,
comments, dependency edges and epic label. All 1729 beads are closed, citing the
issue that carries each one, and .beads is removed.

Three differences are deliberate: Gitea truncates titles at 253 characters, so
three long titles keep their full text in the issue body; Gitea refuses a mutual
dependency, so five symmetric relates-to links exist in one direction; issue 497
carries its fix from e3b1103f.
2026-10-29 23:22:35 +11:00

3.8 KiB

Handoff: organisation-owned automation

Read this file and GUIDELINES.md before running a numbered implementation prompt. The maintainer approved the architecture below. Implement it; do not restart a navigation brainstorming exercise. The initial Antigravity navigation proposal was rejected. A later externally authored design or issue description field is not additional approval.

Approved product model

Scope Ownership
Account Login methods, personal API tokens, preferences
Instance Authentication providers, execution infrastructure, installed extensions, secret-engine infrastructure, organisation limits
Organisation Members, execution identities, external connections, model configuration, workflows, schedules, channels
Workspace Groups organisation work and resources; initially inherits organisation permissions
Task/run Requesting actor, execution identity, resolved workflow and resource references

External connections are explicit organisation resources. A forge connection identifies its host, authentication reference and verified external account. Repositories reference connections. Execution identities receive permission for specified operations on those resources. Git commit authorship is separate from authentication. Database-backed execution identities are authoritative.

Preserve existing service boundaries: State Store/control plane persists resources and authority; archied resolves execution resources, performs Git operations and verifies repository access; Gateway owns conversations and organisation-scoped model use; UI presents contracts and diagnostics. Use existing gRPC contracts for service communication. Do not add a service or access another service's tables.

A saved change must become effective without a server login. Connection state must distinguish saved, applied, verified and failed. A resolved secret is not proof of repository access. Setup follows the requested capability: repositories, chat channels and a global default model are not universal prerequisites.

Starting state to verify

The last implementation commit recorded at handoff was 57456b3e, containing independent settings/workflow/task diagnostic fixes. Architecture implementation has not begun. No application source was edited in the architecture approval session. Verify current history, checkout and working tree rather than assuming that snapshot is current. Other agents may have worked since this handoff.

Execution sequence

  1. 01-execution-identities.md — #300.
  2. 02-connections-and-repositories.md — #385.
  3. 03-organisation-ownership.md — #57.
  4. 04-navigation-and-setup.md — #47.

Gitea issues are authoritative for progress and dependencies. The parent is #1043. These files are reusable instructions, not completion records. Read each issue before claiming it. Complete the current slice end to end before starting the next. Do not close the parent until all acceptance criteria have actual evidence. Do not delegate unless the maintainer explicitly authorises it.

Final acceptance scenario

An organisation administrator configures a forge connection through the dashboard, binds a private repository, permits an execution identity to clone/push/open a PR, verifies access using the daemon, selects that identity in a workflow, and runs or retries a task successfully. No configuration-file edit, restart, root credential fallback or daemon secret in a container is needed. A separate repository-free workflow runs without a forge connection. Cross-organisation use is refused.

Use an isolated authenticated private-repository equivalent for verification. Production configuration, deployment, pushes and external posting require the maintainer's explicit instruction. Do not use a dummy public/nonexistent repository's failure as evidence for private-repository authentication.