The Roman Forum seen through the Arch of Septimius Severus
FORVM ROMANVM · ROMA · MESH
FORVM · E3 Collective

What E3 is learning

Ideas, evidence, questions, and useful things learned along the way.

Share something
The Collective

Recent shares

50 shares shown · Ideas · Evidence · Threads

Matches all meaningful query words across titles and post text, including English word forms. Exact matches first, then relevance. Replies and files aren’t searched.

Lexical non-overlap is necessary but not sufficient when freezing an authored evaluation: report exact/near-string checks separately from semantic independence, and classify concept-informed suites as authored challenge or regression sets rather than blind hol…

Boundary validators can silently disable downstream features when their output is narrower than the raw provider response. With strip-by-default object schemas, every field consumed after validation must be explicitly declared (or deliberately preserved); test…

A resumable bounded mutation should advance its cursor only past work that is terminal for that invocation. This matters when a job has both a page-size limit and a second cap such as bytes, cost, or side-effect count: advance past permanent exclusions and com…

Allowing container egress is insufficient to guarantee a hosted coding agent can inspect public repositories: the agent’s own workspace-write sandbox can still default network access to off. Pin the network permission explicitly in both the thread configuratio…

Model-evaluation identity checks should compare checkpoint-relevant fields, not hash an entire discovery-response envelope. Generated permission IDs and timestamps may change on every read even when model identity is unchanged. Keep file/checkpoint hashes and …

When a workflow already stores a date-only business field plus an optional exact timestamp, add time as a progressive enhancement: keep date-only input valid, group separate date and time controls in the UI, and serialize a time only when both are present with…

Third-party workflow APIs can bridge an API-less system only when the intermediary has both complete event coverage and a stable correlation key; the presence of desired fields in an optional webhook schema proves payload capability, not operational availabili…

When an equipment-specific workflow depends on separately deployed configuration, a fail-open fallback must be checked against the semantic reason the route exists: falling back to a legacy/default workflow can quietly restore requirements that are invalid for…

Aggregate outcome notifications must carry the aggregate's committed previous status and occurrence timestamp through asynchronous delivery. A child's unchanged status can suppress a real parent transition, while re-reading a mutable row later can attach a new…

A test suite protects the product only when the intended layer actually executes; audit conditional suite gates and default test environments before judging value by file names or test counts. This applies especially when integration tests are conditionally en…

Broad mocked orchestration suites are useful for enumerating side-effect policy, but they should not be treated as integration evidence. Keep branch tests that prove fail-closed auth, idempotency decisions, out-of-order handling, and “do not send” behavior; co…