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

New issue

Closed

opened 2026-09-22 09:19:28 +00:00 by kilo · 1 comment

kilo commented

2026-09-22 09:19:28 +00:00

Member

Copy link

Goal

Establish a concise repository-local agent workflow for Creatidy Kernel before K-series implementation starts.

Why

A0 architecture is complete. Further development should use Forgejo Issues as durable work authority and should reuse the proven agent-development practices from the parent Creatidy workspace without importing DemandTrace-specific, private-autonomy, or Markdown-based Program control logic.

Scope

In scope:

update repository AGENTS.md for post-A0 development;
add a minimal Kilo rule set for issue-driven implementation;
add Kilo commands for single-issue implementation, PR review, and durable follow-up issue creation;
add local Kilo configuration/index exclusions where useful;
preserve Kernel architectural invariants and Forgejo authority;
keep the rules understandable to a weaker orchestrator such as GPT-5.6 Luna.

Out of scope:

Kernel product implementation;
K1-K8 issue creation;
Program execution;
M5-B integration;
Scarcity Router product integration;
runtime/model-provider policy;
GUI workflow rules;
DemandTrace-specific rules;
deployment;
main;
releases.

Acceptance Criteria

Forgejo Issues are explicitly the durable task source of truth for Kernel development.
Normal implementation requires an explicitly selected issue.
develop -> feature branch -> PR -> develop is the normal delivery path.
main remains human-controlled.
Issue bodies use durable Goal / Why / Scope / Acceptance Criteria / Constraints / Links structure.
Agent rules contain no DemandTrace-specific behavior.
Agent rules contain no M5-B marker/protocol implementation.
Agent rules contain no Markdown implementation of Program state-machine semantics.
Public Kernel development does not require Scarcity Router.
Existing architectural boundaries from A0 remain unchanged.
make check and relevant repository validation pass.
The change is delivered through one reviewed PR to develop.

Constraints

Keep the rule set small.
Avoid duplicated authority across AGENTS.md and .kilo/rules.
Reuse proven parent-workspace practices, but adapt rather than copy product-specific policy.
Do not create labels, Projects, milestones, or additional planning systems.
Do not create K-series implementation issues in this task.

Links

A0 architecture: docs/architecture/target.md
Successor plan: docs/architecture/successor.md
Parent workflow reference: ../AGENTS.md and ../.kilo/

## Goal Establish a concise repository-local agent workflow for Creatidy Kernel before K-series implementation starts. ## Why A0 architecture is complete. Further development should use Forgejo Issues as durable work authority and should reuse the proven agent-development practices from the parent Creatidy workspace without importing DemandTrace-specific, private-autonomy, or Markdown-based Program control logic. ## Scope In scope: - update repository `AGENTS.md` for post-A0 development; - add a minimal Kilo rule set for issue-driven implementation; - add Kilo commands for single-issue implementation, PR review, and durable follow-up issue creation; - add local Kilo configuration/index exclusions where useful; - preserve Kernel architectural invariants and Forgejo authority; - keep the rules understandable to a weaker orchestrator such as GPT-5.6 Luna. Out of scope: - Kernel product implementation; - K1-K8 issue creation; - Program execution; - M5-B integration; - Scarcity Router product integration; - runtime/model-provider policy; - GUI workflow rules; - DemandTrace-specific rules; - deployment; - `main`; - releases. ## Acceptance Criteria - [ ] Forgejo Issues are explicitly the durable task source of truth for Kernel development. - [ ] Normal implementation requires an explicitly selected issue. - [ ] `develop -> feature branch -> PR -> develop` is the normal delivery path. - [ ] `main` remains human-controlled. - [ ] Issue bodies use durable Goal / Why / Scope / Acceptance Criteria / Constraints / Links structure. - [ ] Agent rules contain no DemandTrace-specific behavior. - [ ] Agent rules contain no M5-B marker/protocol implementation. - [ ] Agent rules contain no Markdown implementation of Program state-machine semantics. - [ ] Public Kernel development does not require Scarcity Router. - [ ] Existing architectural boundaries from A0 remain unchanged. - [ ] `make check` and relevant repository validation pass. - [ ] The change is delivered through one reviewed PR to `develop`. ## Constraints - Keep the rule set small. - Avoid duplicated authority across `AGENTS.md` and `.kilo/rules`. - Reuse proven parent-workspace practices, but adapt rather than copy product-specific policy. - Do not create labels, Projects, milestones, or additional planning systems. - Do not create K-series implementation issues in this task. ## Links - A0 architecture: `docs/architecture/target.md` - Successor plan: `docs/architecture/successor.md` - Parent workflow reference: `../AGENTS.md` and `../.kilo/`

kilo referenced this issue

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

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

kilo commented

2026-09-22 09:28:01 +00:00

Author

Member

Copy link

Bootstrap implementation is on PR #2: #2

Acceptance evidence:

AGENTS.md now makes Forgejo Issues the durable source of truth and requires explicit issue selection before implementation.
.kilo/rules/ contains the adapted task, Forgejo, implementation, local-search, documentation, and validation rules.
.kilo/command/ contains single-issue implementation, read-only independent PR review, and durable follow-up issue commands.
kilo.json, .kilocodeignore, and .gitignore provide the repository-local loader and ignore boundaries.
Delivery is develop -> feature branch -> PR -> develop; main remains human-controlled.
Kernel boundaries and local architecture/ADR authority are preserved. Program execution, M5-B, DemandTrace-specific policy, and private model-routing policy were not transferred.

Validation passed:

make check
make package-check
make audit

The PR is open for independent review; this issue remains open until integration into develop.

Bootstrap implementation is on PR #2: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/pulls/2 Acceptance evidence: - `AGENTS.md` now makes Forgejo Issues the durable source of truth and requires explicit issue selection before implementation. - `.kilo/rules/` contains the adapted task, Forgejo, implementation, local-search, documentation, and validation rules. - `.kilo/command/` contains single-issue implementation, read-only independent PR review, and durable follow-up issue commands. - `kilo.json`, `.kilocodeignore`, and `.gitignore` provide the repository-local loader and ignore boundaries. - Delivery is `develop -> feature branch -> PR -> develop`; `main` remains human-controlled. - Kernel boundaries and local architecture/ADR authority are preserved. Program execution, M5-B, DemandTrace-specific policy, and private model-routing policy were not transferred. Validation passed: - `make check` - `make package-check` - `make audit` The PR is open for independent review; this issue remains open until integration into `develop`.

adrian.tkacz closed this issue

2026-09-22 16:08:52 +00:00

kilo referenced this issue

2026-09-22 16:46:21 +00:00

[Kernel v0] First useful vertical slice #3

~~kilo referenced this issue 2026-09-25 21:23:36 +00:00~~

[K2B] External operation journal, outbox, and artifact durability #13

kilo referenced this issue

2026-10-04 23:00:20 +00:00

[Kernel][G08] Serve authoritative state and reconnectable progress to CLI, Console and notifications #57

kilo referenced this issue

2026-10-05 14:41:21 +00:00

[Kernel][G01 G04 G10] Prove existing harness control and gateway compatibility #47

~~kilo referenced this issue 2026-10-28 20:22:45 +00:00~~

feat: compose independent work SCM CI and knowledge drivers (#105) #111

kilo referenced this issue

2026-10-30 20:19:38 +00:00

Deliver ordinary Program execution with shared pull and managed push handoffs #106

~~kilo referenced this issue 2026-10-30 22:29:49 +00:00~~

feat: coordinate ordinary Forgejo programs in pull and push modes (#106) #112

No Branch/Tag specified

develop

issue-62-installed-compatibility

issue-58-private-outcome-export

issue-57-recovery-preparation-alerts

issue-57-owner-served-state

issue-106-final-authority-dag

issue-106-forgejo-ordinary-execution

issue-105-independent-provider-drivers

issue-59-work-resource-ownership

issue-56-atomic-approval-recovery

issue-56-work-budget-enforcement

issue-103-publish-architecture-backlog

issue-62-platform-reception

issue-55-mi-utilized-reference

issue-52-kilo-offline-proof

docs/conversational-review-policy

issue-60-reception-fixture-plan

issue-62-compatibility-matrix-spec

issue-58-export-rights-spec

issue-57-owner-state-spec

issue-56-task-cost-shapes

issue-90-owned-cancellation

issue-54-product-review

issue-53-runtime-integration

No results found.

Labels

Clear labels

bug

Something is not working

duplicate

This issue or pull request already exists

More information is needed

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Creatidy/creatidy-kernel#1

Reference in a new issue

Repository

Creatidy/creatidy-kernel

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?

Rows
Columns