This is the smaller question. A real local deadline that an existing controller or operating envelope does not meet. It is open. Novelty is unestablished. No field trial has been done. The record below is the longer version.
SOE-Q001 · version 1.0 · 27 September 2026
Where does waiting actually hurt?
Research status: Open question · Novelty unestablished · No field trial completed
The question
Can you identify a real situation in which a device or operator must decide locally before a deadline, and an existing local controller or operating-envelope arrangement does not meet that need?
Why it matters
A faster permission check is useful only if waiting causes a meaningful loss. Before proposing another mechanism, we need to understand a real task, its deadline, and what already works.
What is currently known
Existing systems can assign limits and let equipment operate within them. Some implementations also specify behavior during a communications outage. Local autonomy is therefore part of the comparison, not something we can simply claim to have invented.
What remains unknown
We have not identified a documented case where the proposed approach improves service enough to justify its added cost and complexity against the strongest existing alternative.
Contributions that would help
- An example from operating a fleet, charging site, energy system, communications network, or another constrained service.
- The decision that must be made, the deadline, what happens if it is missed, and the current fallback.
- A source or anonymized trace showing a real delay or outage cost.
- An existing product, paper, or operating practice that already solves the problem.
A useful first contribution: “At this kind of site, this decision has to happen within this time. Today we handle it this way. Here is where that works—or fails.” An observation without a paper is welcome; we will distinguish experience from general evidence.
What would change our minds
Evidence that existing arrangements meet the same requirement closes that case. A documented shortfall with a fair comparison and measurable consequences would justify a focused study.
Start with these sources
- CSIP-AUS v1.2 explainer, May 2025, communication-loss behavior — dated implementation guidance. Reading status: the loss-of-communications section was read in the 27 September 2026 audit. Not independently reproduced. Not a claim about every current product.
- AEMO Project EDGE operating-envelope research — practical allocation questions. Reading status: official report summaries inspected. Secondary report. Not independently reproduced.
- SecuLEx — a preprint proposing exchange of operating limits. Reading status: relevant PDF text read, including market-timing assumptions. Not independently reproduced. A preprint is not a deployed product.
Prompt above the response box
What decision, deadline, or existing solution should we examine?
INTAKE · NOT OPEN
Contributions are not open yet
OFFQuestion record
SOE-Q001 · version 1.0
- Question
- Can you identify a real situation in which a device or operator must decide locally before a deadline, and an existing local controller or operating-envelope arrangement does not meet that need?
- Version / date
- 1.0 · 27 September 2026. First public version of this record.
- Scope
- Included: a documented task, its deadline, the cost of missing it, and the incumbent local controller or operating envelope. Excluded: a new protocol, a new token, hardware purchases, and any claim that local autonomy itself is new.
- Owner
- Editorial owner when a record changes: Chris Taylor, or a reviewer he designates. That names a person, not a panel. Intake is not open, so no contribution is in review.
- Disposition
- Open. Reason: no documented case here yet shows an improvement large enough to justify added cost against the strongest existing alternative. Novelty unestablished. No field trial completed.
- Claims
- Fact within the cited sources: existing systems can assign limits and let equipment operate within them, and some specify communications-outage behavior. Unknown whether any documented case justifies another mechanism. Hypothesis that a specific improvement exists — not established. Not a fact that Society of Explorers has invented local autonomy.
- Assumptions
- A faster permission check matters only if waiting causes a meaningful loss. The comparison includes communication-loss defaults. It does not assume that disconnection leaves every conventional device waiting for a server.
- Baseline
- The strongest existing local controller or operating-envelope arrangement for the same task, including scheduled envelopes and a documented disconnection fallback. SecuLEx is a preprint proposal in that neighborhood, not a result that this question has beaten.
- Contributions
- None. Contributions are not open yet. This is not a count of a community.
- Objections
- Unresolved: existing arrangements may already meet the requirement, which would close that case. No contributor objection is on file.
- Tests
- Proposed, not started. Continue only with a documented requirement and a fair comparator. See the evidence agenda.
- Results
- No field trial. No measurement on this question. Toy arithmetic on the evidence page is an illustration for a different check, not an answer here.
- Revision
- Version 1.0 published 27 September 2026 from the public research handoff after the independent audit. No prior public version of SOE-Q001.
Also read Q2 · Q3 · Evidence · Research · Discuss. Intake is not open.