Asim Aslam
76961d503a
* feat(loop): go-micro now runs on `micro loop` (dogfood its own tool)
Replace go-micro's five hand-written loop workflows with ones generated by
`micro loop init --roles all`, making "go-micro builds itself with micro loop"
literally true rather than aspirational.
- Generate loop-planner/builder/triage/coherence/release.yml via the CLI with
go-micro's cadence and wiring (planner :59, builder :29, coherence 07:00,
release 23:00; CI gate "Harness (E2E)"; token CODEX_TRIGGER_TOKEN; base master;
tag prefix v). The old loop-architect.yml and loop-devrel.yml become
loop-planner.yml and loop-coherence.yml.
- Move the queue to .github/loop/PRIORITIES.md and add .github/loop/NORTH_STAR.md
(a concise steer pointing to internal/docs/THESIS.md), adopting the loop's
convention.
- Preserve go-micro's rich instructions as editable policy in
.github/loop/prompts/{planner,builder,triage,coherence}.md — the architect
founder-lens + adoption steer, the increment builder, harness-failure triage,
and the DevRel changelog/blog pass — faithfully ported from the old inline
prompts. Behavior is preserved; only the mechanism is now generated.
- CLI refinement the migration surfaced: prompts (and NORTH_STAR/PRIORITIES) are
now write-once — `micro loop init --force` refreshes workflow MECHANICS but
never clobbers customized POLICY. Added renderKeep + a test.
- Update internal/docs/CONTINUOUS_IMPROVEMENT.md (renamed workflows, moved queue,
the prompt-file model, and a note that these files are generated by micro loop).
Verified: build, go test ./cmd/micro/loop/..., golangci-lint (0 issues), gofmt;
`micro loop verify` passes; all generated workflows are valid YAML; re-running
init --force is idempotent and preserves policy.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL
* loop: strip prompt editorial comments before posting to the agent
Verification of the migration surfaced that a dispatch workflow posted the
prompt file's leading <!-- editorial --> header to the agent, and __ISSUE__
inside it got substituted too (e.g. "Keep 4242 literal"). Harmless (invisible
in rendered markdown) but unclean and mildly confusing. The dispatch and triage
body construction now strips <!-- --> blocks with `sed '/<!--/,/-->/d'` before
substituting runtime tokens. Regenerated go-micro's workflows; added a test.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL
---------
Co-authored-by: Claude <noreply@anthropic.com>
1.6 KiB
North Star
The direction the loop aligns every increment to. Depth lives in
internal/docs/THESIS.md; this is the short,
operative version the planner and builder read each run.
Mission
Make building an agent as easy as building a service, on one runtime. Go Micro is a holistic agent harness and service framework encapsulating the lifecycle of services → agents → workflows — pluggable, progressive, and AI-native by default.
Right now — developer adoption
The framework's depth is strong; the on-ramp is the gap. Weight the developer experience — a walkable first-agent tutorial, discoverable examples, docs wayfinding, install friction, debugging, the 0→1 and 0→hero path — at least as highly as internal hardening. A developer succeeding on their first agent matters more right now than another conformance/observability/interop increment. Do not let the queue fill entirely with internal depth work.
Guardrails
- One concern per PR; small and reversible.
- The gate is green CI (
go build,go test,golangci-lint,make harness), not human review — keep the suite strong; the loop is only as good as its evaluator. - Off-limits without a human (surface as notes, never auto-merge): breaking public-API changes, brand/positioning/marketing copy, new dependencies, architectural rewrites, product-default changes with broad behavioral impact.
- Stay on
claude/*/codex/*branches; base PRs onmaster. SeeCODEX.mdandinternal/docs/CONTINUOUS_IMPROVEMENT.md.