IT architect in Stockholm. I build local, reviewable tools for repository health, governed AI operations and endpoint work, mostly in the terminal.
Real output from mqlaunch hal brief, the status view in
macos-scripts.
- mq-agent: the core of the MQ stack. Workflows, reviews and release gates with verification receipts.
- macos-scripts:
the terminal entrypoint to the stack, through
mqlaunch. - Atlas Core: a standalone loop engine for routed, evaluated, retryable AI-assisted work.
Every MQ tool follows the same loop: make state visible, score it, gate the action, and keep what was learned.
%%{init: {"theme": "base", "themeVariables": {"primaryColor": "#ffb000", "primaryTextColor": "#1a1205", "primaryBorderColor": "#9a6a1c", "lineColor": "#9a6a1c", "edgeLabelBackground": "#ffe2a3", "fontFamily": "JetBrains Mono, ui-monospace, monospace"}}}%%
flowchart LR
in["endpoint, repo, workflow"] --> signal["signal<br/>repo-signal<br/>mq-image-analyze"]
signal --> score["score<br/>repo-signal"]
score --> gate["gate<br/>mq-agent, mq-mcp<br/>mq-ums"]
gate --> memory["memory<br/>mqobsidian"]
memory --> act["next action<br/>macos-scripts, mq-hal"]
| Repository | Role |
|---|---|
mq-agent |
Orchestrates workflows, reviews, release gates, and repo-owned checks with code-bound verification receipts |
macos-scripts |
Terminal entrypoint and local workflow toolkit |
mqobsidian |
Durable technical memory, reviewed decisions, and compact agent context |
mq-mcp |
Policy-bound MCP runtime for controlled tool execution |
repo-signal |
Structural readiness scores, kept separate from verification evidence, and structured AI context |
mq-hal |
Operator views for repo, stack, release, runtime, and changed-file verification, with safe command routing |
mq-image-analyze |
Extracts operational signal from screenshots and UI states |
mq-ums |
Gated operator surface for IGEL UMS workflows |
A high structure score is not proof that tests passed: verification evidence is
reported as PASS, FAIL, STALE or NOT_VERIFIED, separately from scores.
See the repo-signal verification contract.
Full MQ ecosystem · Operating model
Atlas Core is a bounded task loop, kept separate from the MQ stack on purpose: MQ, GitHub and memory plug in as adapters, not as the core. Experimental.
%%{init: {"theme": "base", "themeVariables": {"primaryColor": "#ffb000", "primaryTextColor": "#1a1205", "primaryBorderColor": "#9a6a1c", "lineColor": "#9a6a1c", "edgeLabelBackground": "#ffe2a3", "fontFamily": "JetBrains Mono, ui-monospace, monospace"}}}%%
flowchart LR
observe --> route --> plan --> execute --> evaluate
evaluate -- "retry / replan" --> plan
evaluate --> finalize
The Journal is where I write about systems, technology and thinking.
Browser-based readiness checks for endpoints, with an optional read-only local helper: browser check · Diagnostics v2 · helper guide.