Three proposals behind Frontier Lab

The wider enquiry

• Improve what the project is doing

  The opening slide asks planning to improve the project before improving its plan. Each proposal changes a different object: the quality of incoming demand, the truth conditions of a delivery claim, or the reusable capability left after handover. Better task sequencing alone would leave those questions unanswered.

  Coverage F01 · Deck slide 1; run report, Verdict.

• Keep the invitation to invent open

  The original challenge used ten enquiries as examples of value, feasibility, surprise and innovation. Their ingredients were not a menu to rearrange. The intended move was to appreciate those qualities and propose genuinely different enquiries with comparable or greater promise. Lawrence’s October clarification describes the early proposals as a generous offering of possibilities, still worth examining in their immature form.

  Frontier Lab is one inspectable item in that collection. Its six lenses neither define the foray nor complete its ambition. A later enquiry may propose an unfamiliar purpose or method, and need not combine these lenses into one planner.

  Coverage F02 · Original challenge and Lawrence’s clarification, 3 October 2026; run report, Verdict.

Project Demand Destruction Engine

The first proposal asks whether a desired outcome needs the project currently being proposed. Its useful output is a reasoned choice to proceed, narrow the project or satisfy the need another way.

• Begin with the outcome

  Capture the intended outcome, constraints, pain and sponsor before generating a work breakdown. Ask which outcome could be achieved without a new project. This separates a need from the solution that has acquired a project label.

  In Skarra, one public observing weekend is different from fully restoring the dome, rescuing every archive item or enabling remote observations. A smaller intervention must say which need it meets and what it leaves unresolved.

  Coverage D01 · Deck slides 2–3.

• Generate alternatives to mobilisation

  Search cancellation or deletion, combination, shrinking, substitution, standardisation, automation, negotiation and reuse before deciding to proceed. The deck and report use slightly different lists; together they call for more than a simple “keep or cut” choice.

  A hired portable telescope might substitute for the damaged dome for one weekend. Combining transport loads might reduce boat demand. A remote session might meet an education objective while leaving physical reopening unmet. Each is a candidate whose consequences need inspection.

  Coverage D02 · Deck slides 2–3; run report, idea 1.

• Expose negotiable constraints and existing capacity

  Ask which constraints are self-imposed and which existing asset, policy or agent could absorb the work. Keep a constraint ledger and substitution map so an attractive alternative does not quietly discard an obligation.

  Winter ferry access, a safe visitor route, a preferred restoration standard and a possible charter arrangement have different meanings. The first two may limit feasible work; the others may admit negotiation or a smaller intervention.

  Coverage D03 · Deck slides 2–3.

• Price reversibility

  Identify the smallest irreversible commitment that can be delayed. Compare delay cost, option value, dependency load and friction. Waiting can preserve a useful option, but it can also consume the last access window. A reversible inspection or trial should earn its place through what it can change.

  The original proposal names these considerations without supplying calibrated weights or an optimisation formula. Frontier’s illustrative comparisons make assumptions inspectable; they do not establish their real values.

  Coverage D04 · Deck slides 2–3.

• Choose the minimum sufficient intervention

  Proceed with a full project only when it beats smaller interventions on the required outcome and constraints. Produce a project, no-project or narrowed-project decision, the supporting substitution map and constraint ledger, and one smallest test before full mobilisation.

  For the observatory, the decision brief should distinguish the public weekend from longer-term restoration and identify the next inspection, booking check or trial that could change the choice.

  Coverage D05 · Deck slide 3.

• Keep the rejected-demand receipt

  Record what was rejected and why, alongside the chosen intervention. The receipt allows a future reviewer to reconstruct the reasoning, revisit changed assumptions and see which obligations were deferred rather than solved. It should contain evidence and a next action, not only a lower effort total.

  Coverage D06 · Deck slides 2–3.

• Test the portfolio implication

  The opportunity is to reserve scarce delivery capacity for work that genuinely needs a project. The original pilot proposes taking ten live proposed projects and requiring a no-project, shrink and substitute option for each before any work-breakdown exercise.

  A useful evaluation would inspect outcome sufficiency, rejected-demand reasoning and subsequent commitments. A synthetic reduction in effort points does not demonstrate realised savings, successful substitution or better portfolio decisions.

  Coverage D07 · Deck slide 4.

Truth-Sensor Planning

The second proposal turns a plan into claims that reality can contradict. Evidence has to support the assumed world in which the plan works, and detected drift has to change a decision or action.

• Attach evidence to important claims

  Extract claims from milestones, dependencies, assumptions, handoffs, gates, risks and dates. Give each important claim a sensor, a confidence state and a trigger for changing the plan. Keep the claim distinct from the activity intended to establish it.

  A completed repair task, for example, does not itself establish a safe route for visitors. The relevant inspection, its result and its currency matter.

  Coverage T01 · Deck slides 5–6.

• State what would contradict the plan

  Ask what would be observed if a dependency were slipping and which ordinary traces would reveal it early. Documents, meetings, decisions, messages, tickets and schedules can supply evidence. A sensor needs an observable falsifier as well as a hoped-for confirmation.

  A cancelled ferry slot, failed access inspection or missing telescope booking can contradict a claim about the weekend even when the completion report remains positive.

  Coverage T02 · Deck slides 5–7.

• Distinguish stale evidence, contradiction and silence

  Update belief, staleness, contradiction and silence separately. Evidence from an earlier state may no longer support the current one. An overdue expected observation differs from an explicit failure; repeated reports derived from one observation do not necessarily provide independent support.

  The source proposes this discipline without specifying a probability model. The demonstration uses explicit states and thresholds, so it should not be read as a calibrated forecast.

  Coverage T03 · Deck slides 5–6. The independence caution is a demonstration boundary, not an additional result from the deck.

• Challenge a convenient green status

  Look for unsupported but socially convenient claims, “fake green”, orphaned risks and changed assumptions. Keep the official narrative visible beside its evidence state so a contradiction can be examined instead of disappearing into a reassuring aggregate.

  A sponsor’s declaration, a current certificate and an authorised gate decision are different things. Evidence can make a case eligible for review without giving an agent the authority to reopen the site.

  Coverage T04 · Deck slides 5–6. The authority distinction is explicit in Frontier’s construction.

• Turn drift into action

  Convert a material change into a decision, probe or plan revision. A weak claim may call for a fresh inspection, confirmation of a booking, a narrower opening or delayed commitment. Merely flagging it again in a dashboard would stop short of the proposed mechanism.

  Coverage T05 · Deck slide 6.

• Build a lightweight evidence routine

  The proposed outputs are a dashboard of truth state, a weekly evidence refresh and contradiction review, and decision gates based on live support. Ordinary project residue is the starting material. A comprehensive digital twin is not a prerequisite for instrumenting ten consequential claims.

  The opportunity is a repeatable review that exposes unsupported assumptions early enough to act. The demonstration neither provides comprehensive assurance nor certifies a real opening.

  Coverage T06 · Deck slides 6–7.

• Compare findings with the official narrative

  The original pilot starts with one troubled project, instruments ten claims, runs a weekly sensor pass for four weeks and compares its findings with the official status narrative. This comparison could reveal whether the extra discipline finds consequential drift earlier or merely adds reporting work.

  Improved detection, useful decisions and safer delivery would need observation. A coloured state changing in this fictional example establishes none of those outcomes by itself.

  Coverage T07 · Deck slide 7.

Project Capability Compiler

The third proposal treats project work as raw material for a reusable method. Completion includes a packet another team or agent can run, with evidence about its limits.

• Deliver the work and preserve the method

  Ask which delivery move is newly reusable and what would let a future team or agent repeat the good part faster. The target is a capability packet that can actually be used. A collection of observations or a polished lessons-learned summary is only an input.

  Coverage C01 · Deck slide 8.

• Harvest reversals and judgement calls

  Capture decisions, artefacts, reversals, judgement calls and hard-won exceptions while the work is fresh. Preserve the failed or rejected move as well as the successful one. Knowing why full dome restoration was deferred, for example, may be more reusable than a record that portable telescopes were hired.

  Coverage C02 · Deck slides 8–9.

• Separate a recurring pattern from its conditions

  Cluster what repeats and identify what only works under particular conditions. A limited-access decision rule may transfer; an island’s tide threshold or ferry contract may not. The packet should identify the general method, its prerequisites and the local choices that must be replaced.

  Coverage C03 · Deck slide 9.

• Package something usable

  The source names playbooks, prompts, templates, schemas, data models, interfaces, diagrams, tests, instructions, skills and demos as possible surviving forms. Choose the form that helps someone perform the move. A useful packet describes its inputs, procedure, output, prerequisites, exceptions and example checks.

  Frontier’s compiler uses the selected demand and evidence context to build a bounded packet. It does not claim to have generated every artefact form named in the original proposal.

  Coverage C04 · Deck slides 8–9.

• Test transfer on a different scenario

  Record evidence that a move worked, failed or required conditions, then run a small transfer test on another project or scenario. A second scenario should be able to expose a mismatch and reject or adapt the packet, rather than merely endorse it.

  A hilltop station facing winter-road closure may share a limited-access decision with an island observatory. It still needs different access evidence. A synthetic pass demonstrates consistency with declared conditions; independent reuse would be a further result.

  Coverage C05 · Deck slides 8–9.

• Publish the packet with its proof and boundaries

  The original proposal files a packet into a local knowledge collection, repository, skill library or service catalogue. Keep its reuse test and boundary conditions beside it, with version and source context, so another user can inspect the claimed capability.

  Exporting a packet, passing an illustrative test and demonstrating repeatable use are separate events. The browser offers a reviewable artefact; it does not silently turn that artefact into a validated organisational capability.

  Coverage C06 · Deck slide 9.

• Examine the accelerator or offer

  The proposed opportunity is accumulated methods, stronger agents, a future project accelerator or a client offer. Delivery experience could outlast the temporary organisation that produced it.

  To pursue that possibility, identify who could use the packet, the task it helps them perform, the conditions of use, and what recipient evidence would establish value. A saved method is a candidate asset. It has not yet demonstrated reduced effort, adoption, acceptance or a purchasable service.

  Coverage C07 · Deck slides 9–10.

• Keep the original generative pilot

  The original first pilot uses the deck as run 1, reruns the same challenge with a materially new model, asks for three stronger ideas and records whether it discovers a genuinely higher-order project form. The run report urges later attempts to go beyond recombining formal planning methods.

  The present compiler is a new illustration of one candidate. It neither replaces that open challenge nor demonstrates that a model has learned a durable capability from the project.

  Coverage C08 · Deck slide 10; run report, Verdict.

Original ratings and source integrity

These are the deck’s own July 2026 proposal ratings out of five. They are historical judgments of promise, with no independent validation or measured result behind them.

The run report calls the proposals a strong first frontier and judges them feasible using notes, project artefacts, agent prompts, schedule/status residue and lightweight dashboards. Its claims about rendering and overflow concern the deck. Its references to automation and local filing describe that historical run.