Skip to content
OBSERVATION NOTES

Industry Architecture

Enterprise digital workforce, agent platforms, control planes and work-management architecture.

70observation notes
Observation note list70 shown, sorted newest first
01
Daily ObservationEngineering InsightAwaiting review

Where Check Fields Come From: The Evidence Boundary of Multi-Agent Acceptance

Isolated function probes distinguish storing a check verdict from performing verification. Acceptance interfaces need to expose who generated a field, which proposition it covers and what evidence remains missing.

→
02
Daily ObservationEngineering InsightAwaiting review

An Approval Prompt Is Only One Part of Delegated Authority

Pinned source-function probes show how approval changes action disposition, while leaving caller identity, authority scope and policy coverage as separate evidentiary questions.

→
03
Daily ObservationExperiment ReportAwaiting review

The Same Workflow Results Can Produce Different Rankings

Across 25 released configurations, partial score and complete acceptance reverse 34 pairwise orderings robustly to rounding. Domain weighting reverses six more, only three beyond rounding uncertainty. State the success objective before interpreting the ranking.

→
04
Daily ObservationResearch NoteAwaiting review

A closer match is not always a better fit for the task

Two-dimensional counterexamples using explicitly chosen formulas show that irrelevant added capability or relaxed requirements can lower similarity while satisfaction scores stay unchanged. Internal demonstrations also separate score stability, choice stability and feasibility; they neither reproduce the original study nor establish real-task benefits.

→
05
Daily ObservationTechnical AnalysisAwaiting review

Minimal authority may have multiple answers: what must an approval specify?

Synthetic enumeration retains two incomparable minimal grants; approval needs the actual footprint and an explicit selection objective.

→
06
Daily ObservationTechnical AnalysisAwaiting review

Completion, legality and safety: why three metrics cannot stand in for one another

Pinned evaluation modules allow full goal progress with failed acceptance, and a legal plan with a safety violation. Synthetic inputs expose predicate scope, not full-system performance.

→
07
Daily ObservationExperiment ReportAwaiting review

Why more procurement threads can perform worse at the same acceptance probability

A fixed-marginal internal model counterexample shows why procurement concurrency depends on branch dependence and excess-acceptance costs, rather than information-processing speedup.

→
08
Daily ObservationExperiment ReportAwaiting review

Does Parallel Review Still Pay Once Compute Counts?

A cost sensitivity calculation on reported synthetic-document review rates shows how resource charges change choices and how rounding limits architecture rankings.

→
09
Daily ObservationExperiment ReportAwaiting review

An Approval Can Be Spent Before an Effect Is Delivered

Source-derived isolated database probes admitted one consumer per race. Intentionally omitting the subsequent effect left retry refused, separating consumption evidence from external delivery and crash recovery.

→
10
Daily ObservationTechnical AnalysisAwaiting review

The approval is spent. Was the effect delivered?

Isolated probes share one consumed-approval state across success, pre-effect failure and post-effect exception. Replay control and delivery evidence require separate accounts.

→