[Governance] Establish issue-first agent development workflow #2

Merged

adrian.tkacz merged 1 commit from issue-1-agent-workflow into develop

2026-09-22 10:59:31 +00:00

kilo commented

2026-09-22 09:27:48 +00:00

Member

Summary

Establishes the post-A0 repository-local agent workflow for Creatidy/creatidy-kernel.

Changes

Replaces A0-only AGENTS.md guidance with concise issue-first, Forgejo-canonical delivery rules.
Adds six minimal .kilo/rules/ files for task authority, Forgejo boundaries, implementation discipline, local search, documentation, and validation.
Adds /implement-issue, /review-pr, and /create-follow-up-issue commands for normal single-issue work.
Adds repository-local kilo.json and .kilocodeignore configuration.
Unignores only committed .kilo/rules/*.md and .kilo/command/*.md paths while keeping local Agent Manager state ignored.

Acceptance Evidence

Forgejo issue #1 is the selected durable task authority; normal work requires explicit issue selection.
Delivery is documented as develop -> feature branch -> PR -> develop; main remains human-controlled.
Issue quality requires Goal / Why / Scope / Acceptance Criteria / Constraints / Links.
Rules preserve adapters -> ports -> core, local architecture/ADR authority, and self-contained operation without private runtime, M5-B, or mandatory Scarcity Router dependencies.
Program execution, M5-B protocols, DemandTrace-specific policy, and private model-routing policy were not transferred.

Validation

make check passed: formatting, lint, basedpyright, import boundaries, 15 tests, secret scan, and diff check.
make package-check passed.
make audit passed with no known vulnerabilities.

Refs #1

Do not merge automatically; independent review is required before integration into develop.

## Summary Establishes the post-A0 repository-local agent workflow for `Creatidy/creatidy-kernel`. ## Changes - Replaces A0-only `AGENTS.md` guidance with concise issue-first, Forgejo-canonical delivery rules. - Adds six minimal `.kilo/rules/` files for task authority, Forgejo boundaries, implementation discipline, local search, documentation, and validation. - Adds `/implement-issue`, `/review-pr`, and `/create-follow-up-issue` commands for normal single-issue work. - Adds repository-local `kilo.json` and `.kilocodeignore` configuration. - Unignores only committed `.kilo/rules/*.md` and `.kilo/command/*.md` paths while keeping local Agent Manager state ignored. ## Acceptance Evidence - Forgejo issue #1 is the selected durable task authority; normal work requires explicit issue selection. - Delivery is documented as `develop -> feature branch -> PR -> develop`; `main` remains human-controlled. - Issue quality requires Goal / Why / Scope / Acceptance Criteria / Constraints / Links. - Rules preserve `adapters -> ports -> core`, local architecture/ADR authority, and self-contained operation without private runtime, M5-B, or mandatory Scarcity Router dependencies. - Program execution, M5-B protocols, DemandTrace-specific policy, and private model-routing policy were not transferred. ## Validation - `make check` passed: formatting, lint, basedpyright, import boundaries, 15 tests, secret scan, and diff check. - `make package-check` passed. - `make audit` passed with no known vulnerabilities. Refs #1 Do not merge automatically; independent review is required before integration into `develop`.

kilo added 1 commit

2026-09-22 09:27:48 +00:00