mrcharles
721968bc3b
Bring the framework's global baseline (BASELINE-PROMPT.md, PATTERNS.md, ADOPTING.md) into the repo — AGENTS.md referenced them but the files were missing. AGENTS.md gains three rules adopted this session: TDD & Linting (mandatory at the Ansible/IaC transition), IaC codification shadow-tracking (every manual fleet change same-day ticketed to #454), and Redmine tracker discipline (Support not Bug — the CLI default created nine misfiled tickets, now corrected). Q10 records the direct-push vs PR conflict for the founder to rule on. 💘 Generated with Crush Assisted-by: Crush:glm-5.2
61 lines
3.4 KiB
Markdown
61 lines
3.4 KiB
Markdown
# questions-v2.md
|
|
|
|
> Git-tracked question log. The agent writes; the human reviews/edits inline.
|
|
> Version up when a round of answers lands. Synthesize resolved Q&A to Discourse/Redmine.
|
|
> See BASELINE-PROMPT.md §9.
|
|
|
|
## Resolved (from v1)
|
|
|
|
### Q1. Git remote for meta? — RESOLVED
|
|
- **Decision:** New Gitea repo under TSYSGroupCorporate org: `TSYSGroupAIOS`. Template repo. Created and pushed.
|
|
- **Synthesized to:** Meta repo created, `tea` + `docker login` noted as available on workstations.
|
|
|
|
### Q2. The bin/ wrapper gap — RESOLVED
|
|
- **Decision:** No bin/ wrappers. Invoke real containers with `docker run --env-file`.
|
|
- **Synthesized to:** PFVCluster AGENTS.md §CLI access; meta AGENTS.md §CLI invocation.
|
|
|
|
### Q3. Discourse pointer-header pattern — RESOLVED
|
|
- **Decision:** Mandatory for ALL projects. No exceptions. Discourse/Redmine required.
|
|
- **Synthesized to:** Meta AGENTS.md, check-rules.sh enforces.
|
|
|
|
### Q4. Sub-agent nudge hook — RESOLVED
|
|
- **Decision:** No harness-specific hooks. Move to portable git hooks + AGENTS.md protocols. User shifting away from Crush to OpenWebUI/Hermes.
|
|
- **Synthesized to:** All hooks ported to git hooks. No Crush-specific dependencies.
|
|
|
|
### Q5. JOURNAL.md vs Discourse — RESOLVED
|
|
- **Decision:** No more JOURNAL.md. Redmine is SoR for work. Discourse for synthesized knowledge.
|
|
- **Synthesized to:** Meta AGENTS.md, PFVCluster AGENTS.md.
|
|
|
|
### Q6. RackRental split-network design — RESOLVED
|
|
- **Decision:** Keep storage bonds. If 4 NICs total: 2 storage, 1 mgmt non-RackRental, 1 trunked to RackRental VLAN 2.
|
|
- **Synthesized to:** #433 (trunk ports), #432 (VLAN config).
|
|
|
|
## Open questions
|
|
|
|
### Q7. Close #167 (Small UPS Units Re-build)?
|
|
- **Context:** #167 is an old (Dec 2024) vague ticket about rebuilding garage UPS units. It's been superseded by #372 (Tripp Lite physical reseat) and #439 (UPS data integration). Dates are stale (Aug 2025).
|
|
- **Question:** Should we close #167 as superseded?
|
|
- **Answer:** _(human)_
|
|
- **Decision:** _(human/agent)_
|
|
- **Synthesized to:** —
|
|
|
|
### Q8. Friday onsite work order?
|
|
- **Context:** Friday 2026-08-14 onsite batch. Tickets: #341 (TEMPer deploy), #372 (Tripp Lite UPS reseat), #431 (Cisco fan replacement), #414 (tsys5 nic2 cable swap), #374 (PDU outlet renaming), #439 (UPS integration).
|
|
- **Question:** What order do you want to tackle these? Cisco fan (#431) blocks #432/#433/#434/#436 — should it go first? TEMPer is the "fun" project — save for last?
|
|
- **Answer:** _(human)_
|
|
- **Decision:** _(human/agent)_
|
|
- **Synthesized to:** —
|
|
|
|
### Q9. Session-start gate: relax for continuation sessions?
|
|
- **Context:** You mentioned last session wanting to discuss relaxing the ticket gate for handoff/continuation sessions. The scope-alignment gate now handles this (presents handoff priorities, waits for user to name target). Is this sufficient, or do you want further changes?
|
|
- **Answer:** _(human)_
|
|
- **Decision:** _(human/agent)_
|
|
- **Synthesized to:** —
|
|
|
|
### Q10. Git flow: direct-push vs PR workflow (TSYSGroupAIOS conflict)?
|
|
- **Context:** Template says "once work leaves the workstation, it goes through a PR" (tea CLI). This project's policy is ALWAYS commit+push directly to origin/main. Founder's own rule, reinforced all session.
|
|
- **Question:** Keep direct-push for PFVCluster (ops repo, solo operator), adopt PRs for playbook code post-IaC-transition, or hybrid?
|
|
- **Answer:** _(human)_
|
|
- **Decision:** _(human/agent)_
|
|
- **Synthesized to:** —
|