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

document the fresh-machine bootstrap order (context load point, workspace AGENTS.md symlink ownership) #300

New issue
Closed
opened 2026-06-12 07:07:55 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-06-12 07:07:55 +00:00
Owner
Copy link

Context

A low-context review agent flagged that the new-machine bootstrap order is undocumented: per-repo AGENTS.md files lean on globally-loaded workspace context (~/.claude/CLAUDE.md -> agentic-os(-kai)/AGENTS.md), but nothing states what to clone or run first so that load point exists on a fresh host. docs/ansible.md documents the roles (agent-compose, repos, reconcile, the freshness gate) but not the cold-start sequence that gets ansible running in the first place.

Ask

Add a short "fresh machine bootstrap" runbook to docs/ (or a section in docs/ansible.md) covering the ordered chain, roughly:

  1. What to install bare-handed (brew/scoop, coily tap) before any repo exists.
  2. Which repo to clone first (infrastructure? agentic-os-kai?) and from which remote, given Forgejo auth is not yet configured on a cold host.
  3. The ansible invocation that converges ~/.claude/CLAUDE.md (agent-compose), the skill mount, and the workspace AGENTS.md symlink - and note who owns that symlink. On kais-macbook-pro it pointed at the pre-org-split path (~/projects/coilysiren/agentic-os-kai/) and dangled until hand-fixed on 2026-06-12, which suggests no role currently converges it.
  4. The coily setup / coily exec up-to-date pass that finishes the job.

Until the load point exists, the only per-repo orientation a fresh host (or a foreign agent in a standalone clone) has is the managed AGENTS.md pointer block with its absolute URLs - which is also why the pointer migration (see the companion agentic-os issue filed today) matters for bootstrap, not just tidiness.

Filed as an issue rather than a direct edit because other agents are active in this repo.

Origin

Low-context review batch relayed by Kai, 2026-06-12.

## Context A low-context review agent flagged that the new-machine bootstrap order is undocumented: per-repo `AGENTS.md` files lean on globally-loaded workspace context (`~/.claude/CLAUDE.md` -> `agentic-os(-kai)/AGENTS.md`), but nothing states what to clone or run first so that load point exists on a fresh host. `docs/ansible.md` documents the roles (`agent-compose`, `repos`, `reconcile`, the freshness gate) but not the cold-start sequence that gets ansible running in the first place. ## Ask Add a short "fresh machine bootstrap" runbook to `docs/` (or a section in `docs/ansible.md`) covering the ordered chain, roughly: 1. What to install bare-handed (brew/scoop, coily tap) before any repo exists. 2. Which repo to clone first (`infrastructure`? `agentic-os-kai`?) and from which remote, given Forgejo auth is not yet configured on a cold host. 3. The ansible invocation that converges `~/.claude/CLAUDE.md` (agent-compose), the skill mount, and the workspace `AGENTS.md` symlink - and note who owns that symlink. On kais-macbook-pro it pointed at the pre-org-split path (`~/projects/coilysiren/agentic-os-kai/`) and dangled until hand-fixed on 2026-06-12, which suggests no role currently converges it. 4. The `coily setup` / `coily exec up-to-date` pass that finishes the job. Until the load point exists, the only per-repo orientation a fresh host (or a foreign agent in a standalone clone) has is the managed AGENTS.md pointer block with its absolute URLs - which is also why the pointer migration (see the companion agentic-os issue filed today) matters for bootstrap, not just tidiness. Filed as an issue rather than a direct edit because other agents are active in this repo. ## Origin Low-context review batch relayed by Kai, 2026-06-12.
coilysiren commented 2026-06-17 08:22:32 +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:22:33 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
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/infrastructure#300
No description provided.