Add .coily/coily.yaml marker file #3

New issue

Closed

opened 2026-05-26 04:36:49 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-05-26 04:36:49 +00:00

Owner

Problem

atmosphere is missing the .coily/coily.yaml marker that classifies it as a deployment-of-one repo. Per agentic-os-kai AGENTS.md, classification is file-presence: .coily/coily.yaml → coily/deployment-of-one, .agent-guard/agent-guard.yaml → external-facing.

Without the marker, atmosphere can not be cleanly bucketed for the GH-issues-disable sweep (related: coilysiren/agentic-os-kai work to stop dual-filing GH ↔ Forgejo issues).

Plan

Land a minimal .coily/coily.yaml with a catalog block and no commands (atmosphere is a docs/ideas repo, no build verbs). This makes the classification file-backed.

**Problem** atmosphere is missing the `.coily/coily.yaml` marker that classifies it as a deployment-of-one repo. Per agentic-os-kai AGENTS.md, classification is file-presence: `.coily/coily.yaml` → coily/deployment-of-one, `.agent-guard/agent-guard.yaml` → external-facing. Without the marker, atmosphere can not be cleanly bucketed for the GH-issues-disable sweep (related: coilysiren/agentic-os-kai work to stop dual-filing GH ↔ Forgejo issues). **Plan** Land a minimal `.coily/coily.yaml` with a catalog block and no commands (atmosphere is a docs/ideas repo, no build verbs). This makes the classification file-backed.

coilysiren referenced this issue

2026-05-26 04:45:22 +00:00

Sweep pre-existing documentation-layout and code-comments violations #4

coilysiren referenced this issue from a commit

2026-05-26 04:59:41 +00:00

chore: add catalog trifecta (marker, AGENTS, FEATURES, README See also)

coilysiren closed this issue

2026-05-26 04:59:41 +00:00

coilysiren referenced this issue from coilyco-bridge/eco-mods-assets-embeded

2026-05-26 16:50:28 +00:00

Add .coily/coily.yaml marker file #1

coilysiren referenced this issue from coilysiren/algo-zone