One consolidated control surface for the Ehrlich workspace. Supersedes the three
overlapping HTML artifacts (XRAY.html, RADIOGRAPH.html,
generated/SUBSYSTEM_WARROOM…html) and the static CONTROL_MAP.md.
Liveness was verified by probe at generation time; click re-probe to refresh from your own network.
The shortest truth (re-probed 2026-07-06): the hub2 surfaces are alive, and the solvulator.com fleet is
no longer uniformly dark — land.solvulator.com serves 200 from hub2 ("Solvulator Land") and
app.solvulator.com serves 200 from nabla ("Heedless Siblings · Resilient Hyper-PWA"); the other nine
solvulator.com names still point at nabla's dead ingress, and the apex has no A record. The operator's declared
priority (2026-07-06): make solvulator itself come to fruition — the peripheral surfaces are in good shape;
the undecided canonical-line question (Q-001) is now the main blocker, not missing code.
Conformance marking (this iteration): a ⚠ flags a strand that drifted into scope but
breaks the project's stated direction, on three axes — python/node (the doctrine is babashka/Clojure/Rust),
off-direction (not the ECA + solvulator concern), not-in-git (loose / no repo).
Most of the stack is Python under the hood; the clean babashka surfaces (tables, annunciation) are the model the rest should converge to.
Use the ⚠ non-conforming filter to see only the drift.
2026-07-19 partial refresh: this pass added the cleasa strand (WhatsApp/Telegram intake +
tofes-214/218 filing composer) — it did not exist on this map before, despite going live 2026-07-14 — and
updated the lien and debts entries with what this session actually found: a batch of 9 real
tofes-214/218 Google Docs, two provenance bugs caught and fixed in the composer, one case's draft argument
found factually wrong against the live ECA site and corrected, and a long-standing bug in the Telegram bot
where its "live" case data was silently always a hardcoded fallback (the source is login-gated). The other
~13 strands below were not re-probed this pass — they keep their 2026-07-06/07 timestamps.
Current operating truth - 2026-10-04
Since the last refresh (2026-07-19): the deploy rail exists (bb deploy.bb --check reports 8 of 9 declared surfaces up; timeline-public is DOWN because status.solvulator.com serves this board instead); the wireframe chat and the pocket PWA set went live; the case dashboard was re-harvested on 2026-09-03; the July local-cockpit counts (11 procedures, 74 events, 59 decisions) are retired because newer harvests superseded them. The running state is cleasa/NEEDS.md. The public solvulator.com product surface remains unaudited.
- Chat PWAs: draft (ChatGPT-shaped) and relay (WhatsApp-shaped) offer four lines: OpenRouter direct (verified), Gate, Mesh, and any OpenAI-compatible URL. A chat through Gate or Mesh needs the owner's token and has not yet been exercised end to end.
- Why the drift went unseen: the rail checks that a surface answers, not that it serves the bytes in the repo. A served-bytes check and a static-surface type are the next rail changes.
- Not verified: the WhatsApp bot deployed on hub2 on 2026-09-25 (needs one QR scan by the owner); ehrlich.raindesk.dev and ehrlich-v-state.raindesk.dev do not answer today.
- Data rule: facts shown to the user must trace to a source artifact, document hash/path, harvested HTML/JSON, email/correspondence record, or explicit procurement task.
- Auth boundary: keep access/session state, but never store government IDs, temporary passwords, OTPs, cookies, bearer tokens, or raw auth headers.
We built the instruments before charting the territory. This is the territory. The motivating work isn't the software concepts — it's Avrum Ehrlich's whole administrative life, and almost all of it is still fog of war. The one bright corner is the ECA enforcement cases (and even that has a fire in it right now). Click a tile to peek at what we know and what we don't.
Ehrlich's litigation runs on three interwoven tracks — family court (the root matter), ECA enforcement (the liens), and High Court of Justice (petitions against the State). The dated events below are charted from the filings; the rest — hearings, rulings, the full בג״ץ 78240 docket, the family-court matter — is still fog.
The affirmative roadmap. A Gemini-powered legal war-room that ingests Ehrlich's bureaucratic stream and produces the filings he must submit — oppositions to liens (עיקול), court-fee exemptions (פטור), High-Court petitions (עת"ר). The loop: intake → 7-agent Gemini pipeline → filings → deadline tracking. Everything should land on his GCE + Gemini, off the borrowed infra.
- Make solvulator real — operator's declared top priority (2026-07-06): decide the canonical line
(local
solvulator/vshyle-sync/solvulator/), then drive the 7-agent Gemini pipeline against real case docs. Q-001 · D-009 M5 · everything else on this board is periphery to this - Resolve the extracted orphans (
solvulator-fevcm,solvulator-minimap): give git lineage or fold back. D-004 · "real code, fake ownership" Put the workspace root under git— DONE 2026-07-01: root is nowehrlich-hqon private GitLab; control docs versioned & pushed. resolved- Fix the credential gaps: Anthropic key absent from disk (LLM surfaces degrade), Sheets auth ladder dead (stale token + empty key stub). Q-009 · D-009 M4
- NEW 2026-07-19 — Provision a GCP service account for Drive API access on hub2, so both the tofes-214/218 composer and queue_web.bb's reply flow can create real Google Docs autonomously instead of only through an interactively-connected session. Operator is setting this up; steps handed off in-chat. Blocks: closing the "copy to clipboard, no live Doc" gap for good
- NEW 2026-07-19 — Re-verify all 9 tofes-214/218 drafts against LIVE ECA dashboards, not the local case-store snapshot. Case #1 already re-verified and found factually wrong (corrected); the other 8 are unverified and may have the same problem. Needs the operator to paste each dashboard — ECA login is interactive-only, an agent can't do it