Template
The primary value is the knowledge layer (markdown files that any agent reads — Crush, OpenWebUI, Hermes, Conduit on iPhone). CLI tooling (scripts, git hooks) is optional, for projects that use git/docker. Changes: - Remove Makefile entirely. All commands are now direct script invocations (bash scripts/check-rules.sh, bash scripts/setup-hooks.sh, etc.) - Add scripts/test.sh stub (replaces make test) - check-rules.sh: test-suite check now calls scripts/test.sh, not make test - Rewrite README as three-layer architecture: knowledge → git hooks → docker - Update all docs (AGENTS.md, BASELINE-PROMPT.md, ADOPTING.md, PATTERNS.md, STATUS.md) to remove every make reference The framework now works for: - CLI/harness users (git hooks + scripts + AGENTS.md) - Non-CLI users (BASELINE-PROMPT.md loaded into any agent's system prompt) 💘 Generated with Crush Assisted-by: Crush via Crush <crush@charm.land>
1.9 KiB
1.9 KiB
STATUS.md — Agent Scratchpad
Durable, git-tracked scratchpad for token efficiency — NOT the system of record (Redmine is). Agent-owned; human consumes only. See BASELINE-PROMPT.md §8.
Last updated: 2026-08-06
Current State
PRODUCTION-READY. Self-applying. Audit passes clean (17 PASS / 0 FAIL). Pending: push to TSYSGroupCorporate/TSYSGroupAIOS (Q1).
What Just Shipped
- Removed all Crush-specific artifacts (crush.json, hooks/) for harness portability (Q4). Enforcement is now git hooks + AGENTS.md prose only — works under Crush, OpenWebUI, Hermes, or any agent framework.
- Removed docs/JOURNAL.md (Q5). Redmine is the SoR for work; Discourse for docs. JOURNAL.md was a stopgap.
- Added Discourse pointer-header check to check-rules.sh (Q3) — MANDATORY, FAILs if a non-exempt .md lacks a Discourse URL. All projects.
- Fixed CLI references (Q2) — AGENTS.md now documents the real container invocation paths (KNEL-AIMiddleware/{redmine,discourse}-cli/), not the missing bin/ shortcuts.
- scripts/test.sh default is now a no-op pass (template has no tests to run until overridden).
- scripts/check-rules.sh now fully passes on the template itself.
In Progress
- Gitea repo creation (TSYSGroupCorporate/TSYSGroupAIOS as a template) — next.
- PFVCluster adoption guide — next.
Inbox
- (empty)
Blockers / Needs Human Input
- None blocking. All Q1–Q5 answered and applied.
Tactical Notes
- tea + docker login are preconfigured on TSYS workstations (Q1 answer) — projects can self-create repos.
- Redmine↔Discourse split: working notes → Redmine; synthesize durable → Discourse. Per-project which categories/tags.
- Portable enforcement layer = git hooks (pre-commit/pre-push) + check-rules.sh + AGENTS.md. No harness coupling.
Next Actions
- Create TSYSGroupCorporate/TSYSGroupAIOS as a Gitea template repo via tea.
- Push meta to it.
- Write the adoption guide (how an existing project like PFVCluster adopts this).