On this page
Circle · Understand
See what is known.
Compare accounts of the world while keeping who said what, when, on which evidence and how the account changed. Disagreement is useful information—not something to average away.
One job, with clear boundaries.
- Starts with
- Permitted source accounts, original material, timestamps and later corrections.
- Produces
- Attributed observations and comparison: what is known, disputed, missing or revised.
Circle records assertions. Repetition and popularity are not truth, and a sourced observation is not a forecast or advice.
One useful interaction.
- Inspect two accounts of a maker’s delivery performance.
- Compare their dates, evidence and genuinely independent sources.
- Keep the original account and the correction visible together.
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 compare accounts without losing attribution, time, evidence or change history.
- Mission
- Collect permitted sources and make comparison, disagreement, missing coverage and corrections legible.
- Objectives
- Demonstrate source replay, safe publication controls and lossless revision-aware observation handoffs.
- Strategies
- Preserve originals and independent source identities. Source ingestion never counts as permission to publish.
- Measures & triggers
- Measure provenance completeness, observation gaps, correction fidelity and readers’ ability to identify disagreement—not a composite truth score.
- Agents & skills
- Source operations, editorial comparison, adapter engineering and security/release verification need distinct accountable owners.
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.
- Circle delivery plan · 2026-09-24
Distinct responsibilities.
The applied L2 role concerns sourced comparison. It does not absorb every dispatch-L2 function or certify an assertion as true.
- Applied L2
- Sourced IS · observation and comparison
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.