- OAM coverage matrix published on Discourse #309 - questions-v2.md: Q1-Q6 resolved, Q7-Q9 added - aug11.md: replaced with pointer to Redmine #314 + Discourse #309 - Redmine cleanup: 16 tracker fixes, cross-refs, stale ticket reviews - UNPoller InfluxDB noise silenced (config mount fix + disable=true) 💘 Generated with Crush Assisted-by: Crush:glm-5.2
2.9 KiB
2.9 KiB
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 loginnoted 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: —