Roadmap

The roadmap system has been replaced by Forgejo issues.

Forgejo issues are now the operational source for work intake, planning, discussion, implementation triggers, and review handoff for rws-arch-wb. The portal no longer renders a parallel roadmap ledger; it points reviewers to the issue workflow contract and the Forgejo issue queue.

Current Operating Model

• Plan work in Forgejo issues in MoekenIT/rws-arch-wb.
• Use Forgejo labels for type, status, priority, automation intent, gates, and

area ownership.

• Use issue comments for scope tuning, implementation history, and review notes.
• Use issue-linked branches and pull requests as the default delivery path.
• Use agent/implement when an issue is ready for the issue-agent workflow to

prepare an OpenCode implementation run.

• Keep evidence linked from the issue to pull requests, CI runs, artifacts, and

repository paths.

Automation

The issue-first plumbing is defined in these files:

• docs/issue-agent-workflow.md explains the staged intake, readiness,

planning/research, implementation, and review controller.

• workbench/issue-workflow/labels.json defines the canonical label taxonomy.
• workbench/issue-workflow/agent-policies.json defines the deterministic gate

policy, slash-command allowlist, autonomy rules, delivery modes, and frontier-escalation signals.

• .forgejo/issue_template/roadmap-task.yml defines the default work item

template.

• .forgejo/issue_template/decision.yml defines decision issues.
• workbench/issue-workflow/milestones.json defines the initial Forgejo

milestone containers.

• .forgejo/workflows/issue-labels.yml seeds or updates Forgejo labels from the

taxonomy and milestones from the milestone contract.

• .forgejo/workflows/issue-agent.yml reacts to agent/implement and prepares

an issue-agent report. It clones MoekenIT/agent-skills, installs the shared OpenCode skills, agents, commands, and helpers through adapters/opencode/install.mjs, then records the exact agent-skills commit in the run artifact. It stays in dry-run mode until OPENCODE_ISSUE_RUN_ENABLED=1 is deliberately configured for an OpenCode-capable runner.

• .scripts/validate-issue-workflow.mjs validates the issue workflow contract.

Boundaries

• Issue automation may prepare implementation work and evidence, but it does not

approve Confluence writes, real RWS content exposure, or credentialed preview deployment.

• Issues must not contain secrets, tokens, Basic Auth hashes, kubeconfig data, or

copied private runtime values.

• Mirrored Confluence source inputs remain immutable; authored fixes still belong

under workbench/, analysis/, proposals/, or architecture/.

• If an issue touches Confluence credentials, staging, real RWS content, preview

deployment, DNS, TLS, authentication, runners, or platform ownership, add the relevant gate/* label and keep the work blocked until approval is recorded.

Historical Note

Before this replacement, the roadmap lived in docs/roadmap.md and apps/portal/src/data/roadmap.ts. That duplicated planning state is retired in favor of issue-first operation so the project can iterate on the Forgejo workflow early, even while the plumbing is still maturing.