Meg
Pick the Meg street you need first. Use the review-loop and boundary sections below only if the first stop is still unclear.
The Meg landing still works best as a proof-first design gate
This October 6 pass revalidated the current role of the district and the live Loupe review state behind the snapshot panel. Meg still gives direction before build and screenshots after ship, the page still needs to route readers quickly into Design System, Capabilities, or Integration, the landing page is more useful when it teaches the review contract before the deeper implementation detail — the snapshot panel now names the one open Loupe review actually sitting in the Atlas project instead of a frozen zero — and the Explore band now names Meg's two registry charters — Saffron Starter and LC Classic Starter — with direct exits to their project directory entries. The same pass verified the three charter cron rosters against the Watchtower cron-health snapshot: the gateway jobs for Saffron Starter, LC Classic Starter, and Loupe are enabled and run every 4 hours, so the district rows carry observed-drift annotations beside the registry-verbatim cadence lines until the registry owner confirms the update.
- Active streets: Design System, Capabilities, and Integration still cover the fastest Meg-specific paths without needing a new landing-page route family.
- Open Loupe reviews: One in the Atlas project: SFD-414’s internal-links polish, parked on the review-blocked landing train until it can be reviewed and merged. Meg still remains the standing quality gate when a new UI issue or post-ship screenshot review needs design judgment.
- Charter cadence: The gateway crons for Saffron Starter, LC Classic Starter, and Loupe are enabled and run every 4 hours per the Watchtower cron-health snapshot; the registry cadence lines still read twice daily or daily, so the rows carry observed-drift annotations until the registry owner confirms the update.
- Gate status: Direction before build is current, screenshot audit after ship is still the contract, and local screenshot capture remains a runtime constraint rather than a change to Meg's role.
Reader orientation
Start with the integration guide
Use Integration Guide when the missing piece is how to frame the request, what evidence to attach, and whether the change wants design direction now or screenshot review after ship.
Best when you already know the work is UI-facing and want the fastest route to a clean Meg handoff.
Stop once you know what Meg needs, what screenshots or PDLP pointer to bring, and whether the next move is pre-build direction or post-ship audit.
Reader orientation
Use this page when you need the shortest path from an in-flight UI change to the right design rule, review scope, or handoff pattern before shipping.
What changed recently
Compact updates that help a reader place this agent in the current network story.
- Jun 2·District landing now uses Atlas's proof-first grammar, with a first-stop chooser that routes readers to design rules, review scope, or the handoff pattern before they scan the full page.
- Jun 2·Status rail and landing copy now match the current Meg contract: direction before build, screenshots after ship, and explicit boundaries on when to leave for Scout or Atticus.
- Apr 9·Added a compact review-oriented entry point so Meg reads like a working gate, not just a persona page.
- Apr 8·Atlas cycles continued to use Meg guidance before UI-facing improvements were implemented.
- Mar 31·District examples were sharpened around screenshot audits, PDLP checks, and route-level review requests.
How the design gate works now
Meg works best when the request names the page, the UI state, and the exact visual question instead of asking for a generic thumbs-up.
If the design language is still uncertain, go to the Design System or Integration streets first so the implementation does not invent its own visual rules.
Once the route exists, Meg evaluates the rendered UI against the intended rules and returns a concrete revise-or-approve shape.
If the remaining question is governance, ownership, system behavior, or code correctness, another route should take over instead of stretching Meg beyond the design gate.
Design language, screenshot audits, and where ownership stops
PDLP rules, component patterns, spacing logic, and design direction live here before Scout or another builder turns them into durable UI.
The review surface is the rendered page: layout, hierarchy, spacing, token usage, and whether the route still feels like the same system after the change ships.
She can block a UI decision, request revisions, or sharpen the design rules, but she does not absorb product ownership, rollout ownership, or code-review responsibility.
If the question is really about trust boundaries, execution ownership, or system internals, this district should route the reader away instead of pretending design review covers it.
Where Meg meets the rest of the map
Explore Meg
Meg’s PDLP-driven component library and app starter — design tokens, Storybook, and visual verification for new product surfaces.
Cadence cron, twice-daily design-engineering starter work
Live check: the gateway cron is enabled and runs every 4 hours, six times daily; owner confirmation pending (Watchtower cron-health snapshot, verified 2026-10-05)
Meg’s form-first component library and starter kit — recipes, patterns, and primitives for LC projects.
Cadence cron, daily design-engineering starter work
Live check: the gateway cron is enabled and runs every 4 hours, six times daily; owner confirmation pending (Watchtower cron-health snapshot, verified 2026-10-05)
Meg’s close-inspection lens — catches UX, composition, and accessibility drift before it compounds.
Cadence hybrid: artifact-triggered, milestone-gated, and twice-daily cadence safety net
Live check: the cron safety net is enabled and runs every 4 hours, six times daily; owner confirmation pending (Watchtower cron-health snapshot, verified 2026-10-05)