coilyco-flight-deck/backend
2
0
Fork 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

Add fork-dont-PR note to README #4

New issue
Closed
opened 2026-05-23 20:53:50 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-05-23 20:53:50 +00:00
Owner
Copy link

Originally filed by @coilysiren on 2026-05-21T05:56:02Z - https://github.com/coilysiren/backend/issues/76

Problem - this repo is a deployment-of-one: a specific running thing tied to Kai's hosts, identity, or community, not a reusable artifact. Fine to read and fork, but a PR has nothing generic to land against.

Treatment - add a short note near the top of the README, matched to what this repo actually is (homelab / dashboard / dotfiles / profile / site / tap / server automation):

This is my personal <thing>. Fork it freely - but I don't take pull requests. There's no generic artifact here, just my running instance.

Keep it friendly and explain the why. Optional follow-on: branch protection so drive-by PRs auto-bounce.

Parent: coilysiren/agentic-os-kai#676

_Originally filed by @coilysiren on 2026-05-21T05:56:02Z - [https://github.com/coilysiren/backend/issues/76](https://github.com/coilysiren/backend/issues/76)_ **Problem** - this repo is a deployment-of-one: a specific running thing tied to Kai's hosts, identity, or community, not a reusable artifact. Fine to read and fork, but a PR has nothing generic to land against. **Treatment** - add a short note near the top of the README, matched to what this repo actually is (homelab / dashboard / dotfiles / profile / site / tap / server automation): > This is my personal `<thing>`. Fork it freely - but I don't take pull requests. There's no generic artifact here, just my running instance. Keep it friendly and explain the why. Optional follow-on: branch protection so drive-by PRs auto-bounce. Parent: coilysiren/agentic-os-kai#676
coilysiren commented 2026-06-17 08:24:00 +00:00
Author
Owner
Copy link

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.
coilysiren 2026-06-17 08:24:00 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-36
ward-salvage/backend-2a750c77
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
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
coilyco-flight-deck/backend#4
No description provided.