Repository workflow contract

Issue-based work configuration.

This route renders the checked-in issue workflow, label, and milestone definitions. It links to Forgejo issues but does not read live issues, project boards, runner state, seeded labels, or milestone state.

Repository
MoekenIT/rws-arch-wb
configured target
Trigger label
agent/implement
repository contract
Delivery mode
issue-to-pr
configured default
Milestone definitions
5
checked-in definitions

Staged controller

Configured controller stages

These stages describe repository policy. This static route does not establish that a runner or external automation is currently available.

  1. intake

    issues.opened, issues.edited, /agent classify: Deterministically check required label scopes and add safe default metadata suggestions. Output: gate decision, optional label additions, issue comment.

  2. readiness

    status/ready, approval/agent-ready, agent/readiness, /agent ready: Validate explicit staged labels and sensitive gates; authorized /oc --write can apply routine PR labels automatically. Output: allowed or blocked gate decision.

  3. planning/research

    agent/plan, agent/research, /agent plan, /agent research, /oc: Route through cheap-orchestrator for plan or research comments without repository mutation. Output: issue comment and artifact.

  4. implementation

    /oc --write, agent/implement + autonomy/delivery/approval policy, /agent implement, /agent pr: Run cheap-orchestrator through the shared agent-skills OpenCode runtime and deliver normal work through issue-linked PRs. Output: issue-linked branch, PR, validation evidence.

  5. review

    agent/review, autonomy/review, /agent review: Inspect linked PRs, CI, issue evidence, and acceptance criteria without mutating repo state by default. Output: review comment and artifact.

Start here

Forgejo issues are now the work intake, planning, discussion, and implementation queue. Authorized /oc commands are the primary user interface; labels remain audit metadata and safety gates. Live availability and contents are not evaluated by this route.

Default delivery

Use an issue-linked branch and pull request for reviewable changes; direct-to-main remains an explicit future exception, not the default.

Safety boundary

Issue automation may prepare implementation work and evidence, but Confluence writes, real RWS content exposure, and credentialed preview deployment still require separate approval.

State model

Issue lifecycle replaces roadmap task state.

Use labels as the visible state machine and issue comments as the tuning/history thread.

  1. status/triage

    human: Clarify scope, add type, priority, area, gates, and acceptance criteria.

  2. status/ready

    human or agent: Issue is actionable and can be selected for implementation.

  3. agent/implement

    Forgejo Actions: Labeling an issue starts the issue-agent workflow and prepares an OpenCode run report.

  4. status/active

    implementer: Work proceeds through an issue-linked branch and, by default, a pull request.

  5. status/review

    reviewer: PR, CI artifact, and issue discussion are reviewed together.

  6. status/done

    reviewer: Acceptance criteria and evidence are complete; the issue can close.

Milestones

Milestone definitions

These are the checked-in milestone definitions. Whether matching milestone containers exist in Forgejo is not evaluated here.

  1. FGissue milestone

    Forgejo milestone

    M1 - Confluence Cache Foundation

    Dynamic read-only INFRAARCH materialization into ignored local and PVC-backed runtime caches under approved handling rules.

  2. FGissue milestone

    Forgejo milestone

    M2 - Confluence Browser And Rendering

    Portal ability to browse validated runtime-cached Confluence state with hierarchy, safe rendering, context panels, filters, and synthetic review evidence.

  3. FGissue milestone

    Forgejo milestone

    M3 - Preview Site Generation

    Per-PR portal preview sites in the MIT environment with authenticated access, evidence links, cleanup, and rollback proof.

  4. FGissue milestone

    Forgejo milestone

    M4 - Findings Portal

    Clear portal UI and data model for technical findings between Confluence state and workbench state.

  5. FGissue milestone

    Forgejo milestone

    Workflow - IssueOps Foundation

    Forgejo issue, label, project, and issue-agent workflow plumbing that replaces the repository-local roadmap.

Labels

Repository label taxonomy

The checked-in definitions use `/` scopes and mark some scopes exclusive. This route does not verify the current Forgejo label configuration.

state8
  1. exclusive scopestatus/triage

    New issue that still needs shape, labels, or acceptance criteria.

  2. exclusive scopestatus/ready

    Ready for a human or agent to start.

  3. exclusive scopestatus/active

    Work is actively in progress.

  4. exclusive scopestatus/blocked

    Blocked by a dependency, approval, or missing information.

  5. exclusive scopestatus/review

    Implementation exists and needs review or evidence verification.

  6. exclusive scopestatus/done

    Accepted and closed or ready to close.

  7. exclusive scopestatus/planning

    Agent or human planning is in progress before implementation.

  8. exclusive scopestatus/needs-info

    Issue needs more information before planning or implementation can continue.

automation6
  1. exclusive scopeagent/plan

    Ask the agent workflow to analyze and propose an implementation plan.

  2. exclusive scopeagent/implement

    Trigger the issue-agent workflow to start an OpenCode implementation run.

  3. exclusive scopeagent/review

    Ask the agent workflow to review existing changes or PR evidence.

  4. exclusive scopeagent/classify

    Allow the intake stage to classify and suggest missing issue metadata.

  5. exclusive scopeagent/readiness

    Allow the readiness stage to evaluate whether the issue can proceed.

  6. exclusive scopeagent/research

    Ask the agent workflow to research or inspect and comment findings without repo mutation.

classification5
  1. exclusive scopetype/task

    Implementation or delivery work item.

  2. exclusive scopetype/decision

    Decision, policy, or architecture direction needed before work proceeds.

  3. exclusive scopetype/research

    Investigation or evidence gathering work.

  4. exclusive scopetype/bug

    Confirmed defect or regression.

  5. exclusive scopetype/docs

    Documentation or content-only work.

priority4
  1. exclusive scopepriority/p0

    Highest priority; blocks critical delivery or safety.

  2. exclusive scopepriority/p1

    High priority.

  3. exclusive scopepriority/p2

    Normal priority.

  4. exclusive scopepriority/p3

    Low priority or opportunistic cleanup.

gate4
  1. multi-usegate/human-approval

    Requires explicit human approval before completion.

  2. multi-usegate/security-review

    Requires security or exposure review.

  3. multi-usegate/platform-review

    Requires platform, runner, DNS, TLS, or deployment review.

  4. multi-usegate/confluence-access

    Touches Confluence credentials, sync, staging, or real RWS content access.

area6
  1. multi-usearea/source-sync

    Confluence mirror, sync, importer, or source metadata work.

  2. multi-usearea/portal

    Static portal UI, routes, visual QA, or rendering work.

  3. multi-usearea/findings

    Findings model, triage, comparison, or review work.

  4. multi-usearea/preview

    Preview build, deployment, comments, or evidence bundle work.

  5. multi-usearea/validation

    Validators, CI gates, scripts, or quality checks.

  6. multi-usearea/publication

    Publication readiness, approvals, or Confluence-facing outputs.