micro--go-micro
Asim Aslam
31556b310e
* ci: run the architect continuously as the founder lens Make the architect a continuous overseer (hourly at :59, just before the :29 increment) instead of an every-few-days check-in. Each run it tracks live state (what merged, what's in flight), keeps the roadmap priorities live, and judges cohesion across harness/framework/dev-UX plus missing pieces and realignment — re-ranking internal/docs/PRIORITIES.md to match reality. It only opens a PR when the ranking actually changes (otherwise it just posts an assessment and closes its issue), to avoid churn. * thesis: lead the North Star with the mission, grounded in the canon Instill the years of context the loop was missing: the vision lives in the corpus (blog, README, website), not a single doc. Lead THESIS.md with an explicit Mission — "what problem we solve" (make building an agent as easy as building a service, on one runtime, because an agent is a distributed system), distilled from the corpus — and name the blog/README/website as the canon the North Star is a distillation of and must stay faithful to. Wire the architect to judge every priority against the mission and re-derive alignment from the canon, flagging drift in either direction (work vs mission, or thesis vs the blog). --------- Co-authored-by: Claude <noreply@anthropic.com>