On this page
ReFu · Anticipate
Explore what could happen.
Explore possible futures and the evidence that could change your view. A useful forecast shows its assumptions and uncertainty, including when there is not enough basis to assess.
One job, with clear boundaries.
- Starts with
- A defined question, permitted evidence, a time horizon and explicit assumptions.
- Produces
- Inspectable scenarios, evidence-qualified forecasts or an explicit no-assessment result.
A forecast is not a promise, a recommendation or a transaction. Missing probability is not an invented midpoint.
One useful interaction.
- Ask what could delay a particular product launch.
- Compare scenarios and the evidence needed to distinguish them.
- Revisit the assessment when its horizon resolves or its sources change.
The test should include missing evidence, a changed source and a person declining—not only a successful example. Compare usefulness, effort and cost with the existing process.
Direction and delivery · VMOSK-A
A readable overview of the source-owned delivery direction. Vision and mission set the direction; objectives, strategies, measures and skills make the work testable.
- Vision
- People can consider the future without mistaking confidence, prices or presentation for knowledge.
- Mission
- Make scenarios, assumptions, horizons and uncertainty inspectable, with no assessment when the basis is missing.
- Objectives
- Preserve forecast meaning through adapters and evaluate a predeclared cohort against a stated baseline.
- Strategies
- Keep observations, forecasts and any price layer separate. Freeze evaluation and resolution rules before outcomes arrive.
- Measures & triggers
- Report calibration, scoring, sample size, misses and abstentions together; test whether readers distinguish evidence from scenarios.
- Agents & skills
- Forecast authors, independent reviewers, schema engineers and evaluators have separate jobs. Product and policy ownership remain open.
Plan basis and open decisions
This overview does not replace or promote the owning project’s VMOSK-A. Delivery staffing, current KPI baselines and numerical acceptance thresholds require their own source decisions and measurements.
- RealityFutures delivery plan · 2026-09-24
Distinct responsibilities.
Applied L3 forecasting is distinct from the dispatch L3 audit station. Monetary prediction markets require separate decisions and safeguards.
- Applied L3
- Evidence-qualified COULD · inference and forecasts
How the Rosetta correspondence is used
These are documented applied functions, not a ranking of people or a seven-products-to-seven-rows assignment. Their correspondence to Rosetta is an interpretive projection. Dispatch stations review work; they are not new app identities.
The source map preserves the dated applied namespace while its selected successor awaits a separately reviewed migration. Dispatch L5–L7 are counsel, not autonomous execution modes; applied product functions are a different register. A page, plan or model may neither sign nor authorise an action.
Source basis: September 2 level reconciliation, corrected product taxonomy and September 14 owner-selected allocation. Transport, exchange applications and capital products do not acquire unused seats by their position in a catalogue.
Explore the design.
These pages describe the intended product and its delivery work. They do not open a signed-in app or establish operating availability.