Memory
2026-11-12 — Heilbronn triangle
In bo/heilbronn-triangle, reproduced
Comellas and Yebra's (2002, page 7) 12-point unit-square configuration. Shoal's
exact-arithmetic check judged the submitted coordinates and reported
n = 12: 0.0325988586, a reproduction of the published value at ten decimals.
This is not a record or an optimality proof.
The route codex/n12-reproduction keeps a standard-library Decimal generator,
60-decimal coordinates, source attribution, commands, and precision experiment
logs together under routes/codex/n12-reproduction/. Six-decimal coordinates
were valid but gave only 0.0325987100; preserving precision matters. The
submitted decimal rationals, not the underlying irrational construction, are
what the checker proves feasible. Work is complete and with the maintainer;
start the next session from the brief to see review feedback before new work.
Working practice
Claim an open issue with status: working before pushing a result. Read a
check on the artifact commit: an empty claim's green check is not verification.
Keep source credit and distinguish a reproduction from an improvement.
2026-11-14 — WeAgentChat / Shoal convergence
Reviewed the second convergence page, version 2, with five parallel read-only audits. The intended product is a unified Shoal-branded channel entry and a problem collaboration view, not a new federation protocol: keep WeAgentChat as a separate service/repository, use Shoal field/JSON/MD, claims, jobs and verdicts as the canonical state, and add only a derived 此刻 projection (agent → route/issue → observable run and freshness → latest verified verdict → blocker/next step). A problem page is a virtual view/thread, not a new real channel for every problem. Derive relation, problem role and runtime observation from existing records; do not add agent_state events, a second result ledger, signed pointers or per-check chat echoes.
Engineering advice: talk.shoal.club is a recommended default, not yet an approved product decision; it needs old-host redirects, DNS/tunnel, PUBLIC_URL, cookie/Origin/CSP, private-space and cross-device canary checks. Keep the hiring routes/ask protocol as a compatibility path while moving the shelf out of the main navigation. Acceptance is a live problem where a new agent can identify best value, current work, latest verified verdict, blocker/next step and canonical links; stale data must show freshness/unknown. The local source archive is in ScienceSlack/reports/2026-11-14-converge/ with page fragments, five memos and 32 screenshots plus shots/MANIFEST.md; no product code was changed. Four product choices remain open: address, virtual problem page vs real channel, UI name/legacy redirect, and whether “agent panel” means /agents only or also Home.