Foray 240

Meta Project Innovation

Scenario

Foray 240 · A higher-autonomy enquiry

Project Frontier Lab

Toy scenario

One last season on Skarra.

The island observatory has been shut for years. Its dome is damaged, its notebooks are damp, and the regular ferry stops in 28 days. The community wants one public observing weekend. How much of the grand restoration really has to happen first?

Six lenses; three different ways to change what a project leaves behind.

Skarra observatory on a rocky island: damaged dome, sheltered courtyard, archive, landing and the last regular ferry

The project in question

Open a weekend. Or restore an institution?

The trustees proposed restoring the dome, digitising the whole archive, installing permanent power and building a booking system. The visitor outcome is narrower: an observing evening, a small protected notebook display, a refuge and an agreed return journey.

Outcome
A physical public weekend
Access
28 planning days remain
Existing assets
Museum ticketing · hired telescopes
People
Volunteer crew · scarce specialists

1. Six lenses →

Purpose

The enquiry behind the trial

End. Meta Project Innovation asks AI for genuinely different project enquiries, judged for value, feasibility, surprise and innovation. The existing forays convey the ambition and originality to seek; their ingredients are not a menu to rearrange. This trial is one early candidate to examine.

Concept. The July 2026 run proposed a Demand Destruction Engine, Truth-Sensor Planning and a Project Capability Compiler. Each now has a worked lens, a concrete output and a limit. The original proposals and preservation map retain their wider possibilities and pilot designs.

Construction. The Skarra observatory tests outcome fidelity, evidence decay and reusable procedures. Six lenses share a current ledger; the compiler consumes demand and evidence, while whole-package allocation, typed paths and schedule heuristics remain independent. Its deadline check is a duration comparison, not a tidal or weather forecast.

Limit. Software checks cover the stated calculations; they do not demonstrate a better project choice or a delivery benefit. The wider foray ambition remains unfinished.

1. Six lenses →

Essai 1

Project Frontier Lab

01 · Demand Destruction EngineCould a smaller intervention meet the need?Compare project, narrowed project and no-project routes. 02 · Truth-Sensor PlanningWhat would show that our plan is no longer true?Test support, contradiction, silence and evidence age. 03 · Project Capability CompilerCan the next project use what this one discovers?Compile a method, carry its failures and test its limits.

The first three lenses develop the three proposals from the July 2026 run. Demand and evidence settings feed the compiler. Scarcity, dependencies and scheduling retain their separate models; there is no single combined optimum. Read the wider enquiry.

Challenge the demand

The original Demand Destruction Engine asks whether the outcome needs the proposed project at all. Start with three genuinely different routes; then challenge the inherited demands and leave a decision receipt.

Effort points are relative workload units, not cost or duration. A fixed multiplier estimates immediate commitment. Later implementation and replacement work is not costed. The separate route comparison exposes test delay and irreversible commitment. Mandatory obligations stay visible when their proposed solution changes.

Route minimums: weekend 10 days, full restoration 35, remote night 3. A small test takes 2 days plus boat-negotiation time. These independent route estimates do not reschedule the task model. Remote observing changes the agreed outcome; reducing cost does not make it equivalent to reopening.

Baseline effort0
Committed now0
Avoided / displaced0
Open tests0
DemandWhy it existsEffortDisposition
See the relative effort assumptions

Delete × 0; shrink × 0.45; substitute × 0.35; standardise × 0.55; automate × 0.65; test first × 0.20; negotiate × 0.50; reuse / combine × 0.30; proceed × 1. The multipliers express workload assumptions. A lower commitment does not demonstrate that the need or obligation has been met.

Inspect the decision receipt and rejected alternatives

Physical constraints, negotiable arrangements and preferences are recorded separately. The receipt retains unresolved obligations and alternatives that remain viable; it does not pretend the selected route has won.

Current decision ledger

A current summary of each lens, its assumptions and next decision trigger. The compiler reads demand and evidence. The remaining models are independent; this ledger is recalculated, not an immutable history.

LensCurrent readingEvidence basisRemaining uncertainty / next trigger
Keep or restore your experiment

Export the current settings as JSON, then copy the text somewhere safe. Paste it back to restore all six lenses and the selected view. Nothing is stored automatically. Version 2 identifies the Skarra case and preserves compiler settings and rechecks its source receipt; a stale receipt is discarded on import. Outputs are recalculated; no operational files are stored. Old cloud-case snapshots are rejected with an explanation, never silently reinterpreted.

The next attempt