Source library
Keep original passages, dates and attribution close to every account.
Circle · Vision
See who said what.
Understand the world through accounts you can inspect, compare and correct.
Explore Circle
Product design in development. What you can explore today.
Mission
Maintain sourced observations with their attribution, timing, uncertainty and correction history, and make them usable by readers and other products.
One of Skyzai’s seven product strategies, designed to contribute to outcomes for Me (individuals), We (organisations) and They (machine intelligence).
Rosetta agent row · Epistemology
What could justify this claim?
Circle makes the basis of an account inspectable through original sources, attribution, comparison and correction.
Objectives
- Find the original source behind an account.
- See disagreement and distinguish independent sources from repetition.
- Follow corrections while keeping the earlier record.
Strategy
Present source passages side by side; preserve source identities and revisions; expose syndication and disagreement; append corrections; record who made any exclusion or publication and why.
Compare accounts
Read separate accounts side by side, including where they disagree.
Follow corrections
See how a claim changes without losing who said what before.
KPIs
Proposed measures of progress
Measure whether readers correctly identify attribution, disagreement and missing evidence; whether corrections reach the relevant views; and what failed, remained unavailable or was missed.
These measures describe how to evaluate this product’s contribution. Each needs a defined scope, observation period and evidence.
- Targets
- Not set. Thresholds remain to be agreed for the proposed measures.
- Performance observations
- No measured results are recorded here for these proposed measures.
Proposed measurement definitions. Observations are Not recorded and targets are Unset. No collection is connected here; a fictional case is not product performance evidence.Attribution completeness · definition and limits
Origin and uncertainty comprehension · definition and limits
Correction visibility and freshness · definition and limits
Current source availability · definition and limits
Launch evidence
Dated measurements of product launches, live integrations and published customer outcomes have not been recorded here. Missing evidence is not a measured zero.
- Released services
- Not recorded
- Live product integrations
- Not recorded
- Published customer outcomes
- Not recorded
Historical declaration · . Owner direction, 18 October 2026. An owner-specified zero-release baseline was recorded for planning. It is retained as source history and is not a measured product result.
Agents
The Rosetta agent row connects this product’s field of inquiry to occupations, skills and responsibilities. The occupations below describe specialist work; different people, models and tools may carry these capabilities within an explicit assignment.
Rosetta agent row. Product L2 · Epistemology
Responsibility. Sourced observations and comparison
Reasoning approach. Comparative and inductive inquiry: look for similarities, differences and counterexamples across accounts. A pattern is a question to investigate; repetition alone establishes neither truth nor cause.
Source researcher
Skills and responsibilities. Finds and organises attributable material, with gaps and access limits visible.
Input. Permitted originals, capture metadata and access results.
Output. Source records with publisher, author, passage, revision, publication/capture time and unresolved gaps.
Limit. Cannot invent missing evidence or bypass access. A capture does not establish current truth.
Comparison editor
Skills and responsibilities. Distinguishes what each source asserts and whether accounts repeat the same origin.
Input. Attributed source records, model/provider metadata and known origin links.
Output. Claim-by-claim comparisons with contradictions, dependent repetitions and unknown lineage visible.
Limit. Agreement is not independent corroboration. No cause, likelihood or decision is asserted.
Corrections editor
Skills and responsibilities. Connects updates to the affected accounts and preserves the history of the change.
Input. Identified corrections, earlier revisions and known affected answer/draft IDs.
Output. Appended correction links, stale-view flags and evidence updates for separate fresh assessment.
Limit. Cannot rewrite history, find every unknown consumer, publish without permission or approve a downstream proposal.
Required capabilities include source custody, comparison/editorial work, contract engineering and independent evaluation. Actual appointments and capacity must be established separately.
These are roles and skills in development, with a defined context and an output to inspect. Their performance needs evidence and evaluation; a role description does not give an agent permission to act.
See it in a piece of work.
Can the workshop rely on this compatibility claim?
North Workshop is considering an actuator for continuous work. Compare the supplier’s account with a bench observation, then follow a correction into a fresh answer and a changed proposal.
Fictional local example. All names, passages and dates below are authored examples. These controls send no requests, call no models and save nothing beyond this page session.
Inspect the accounts, then make an attributed answer.
Read the source records
Different accounts can disagree. A captured passage shows what its publisher asserted; it does not settle whether the claim is true.
Original supplier assertion
Actuator R / Controller C datasheet
- Publisher / author
- Rowan Engineering / Supplier technical desk
- Source / version
- supplier-A / A
- Published / captured
- /
Actuator R supports continuous operation with Controller C.
A supplier statement; the operating conditions are incomplete.
Current supplier access: Available in this example. Revision A is the latest revision known in this example.
Separate observation
Bench observation, run NW-17
- Publisher / author
- North Workshop / Workshop test team
- Source / version
- workshop-1 / 1
- Published / captured
- /
In our 30-minute bench run, R stopped after 12 minutes with Controller C, firmware 1.2, a 24 V supply and no adapter.
One fictional bench observation. It does not establish cause or performance in other conditions.
Stale capture; current page inaccessible
Retained catalogue entry
- Publisher / author
- Rowan Parts reseller / Catalogue editor
- Source / version
- reseller-0 / 0
- Published / captured
- /
Controller C is listed as compatible with Actuator R.
Last successful access: 2 August. Current access failed in this example on 21 October. Current content and origin lineage are unverified; this is not current corroboration.
Two model summaries, one supplier origin
Illustrative model summary One: “Continuous operation is supported with C.” Provider Example One, model Summary One v0, authored 15 October 2026; input supplier-A. No model was called.
Illustrative model summary Two: “The supplier says R works continuously with C.” Provider Example Two, model Summary Two v0, authored 16 October 2026; input supplier-A. No model was called.
Both derive from supplier-A. Neither reports a separate observation. Two model outputs plus their source remain one supplier origin. Agreement is not independent corroboration. The workshop record is a separate account; the reseller’s lineage is unknown.
Follow the correction
Append the supplier’s later correction. Earlier accounts, answers and proposals keep their original sources.
Carry evidence into fresh work
Circle supplies the attributed comparison. The downstream recommendation below illustrates a separate Agentz draft; a person must review any next step.
Attributed answers
No answer prepared. Inspect the source records first.
Downstream drafts
No draft staged. A fresh answer is required.
What this example can and cannot establish
The correction flags only the answers and drafts shown here. It does not discover unknown consumers or update an external system. This exercise has no live Circle feed, provider account, inference spend, publication, storage or permission grant. Reload or reset starts the authored example again.
One job, with clear boundaries.
- Starts with
- Permitted source accounts, original passages, timestamps and later corrections.
- Produces
- Attributed observations and comparisons, with independent sources distinguished from repeated accounts.
Circle records assertions. It asserts no cause and no likelihood. Publication requires its own permission; repetition and popularity do not establish truth.
Capabilities and current proof.
As reviewed on , these are selected capabilities traced to their product owner. The proof level describes a plan, source observation or bounded test; it does not establish a released service.
Attributed source evidence · Source observed
Local and hosted case adapters name Circle as an external evidence source and preserve attribution.
Current limit: Circle was unavailable from the inspected host; adapter code does not prove a reachable live Circle service.
Comparison, disagreement and correction · Bounded local proof
The local synthetic case retained corrected records and flagged dependent work for review.
Current limit: This proves a host correction flow with illustrative inputs, not a released Circle comparison service.
Product plan, responsibilities and sources
Direction and delivery
Skyzai’s vision is an emergent Marketsphere. Its mission is to develop SPECTRE as an open operating system for it. Me, We and They describe the participant objectives, and each of the seven products is a strategy with its own KPIs and Agents. This nested product plan explains its direction, objectives, delivery work, measures and responsibilities; customer outcomes remain to be demonstrated.
- Vision
- Circle records who asserted what. Circle asserts no cause and no likelihood.
- Mission
- Maintain sourced observations with their attribution, timing, uncertainty and correction history, and make them usable by readers and other products.
- Objectives
- Let readers inspect originals, compare rival accounts, distinguish independent sources from repetition, recognize missing evidence and follow corrections without losing earlier versions.
- Strategies
- Present source passages side by side; preserve source identities and revisions; expose syndication and disagreement; append corrections; record who made any exclusion or publication and why.
- Measures & triggers
- Measure whether readers correctly identify attribution, disagreement and missing evidence; whether corrections reach the relevant views; and what failed, remained unavailable or was missed.
- Agents & skills
- Required capabilities include source custody, comparison/editorial work, contract engineering and independent evaluation. Actual appointments and capacity must be established separately.
Plan basis and open decisions
Current owner direction defines product responsibilities. Retained proposals inform delivery plans and engineering work. Signed charters, current operating mandates, staffing and measured baselines retain their separate standing.
- The source-owned first engineering proof retains one admitted RSS source and its full 30-day observation and correction record. Reader comprehension needs a separate evaluation.
- An older charter allows a separately labelled inference mode, while the later product row calls for comparison without inference between accounts. This proposed overview follows attributable comparison and preserves that source conflict.
These working documents require access to the corresponding private GitHub repositories.
- Reviewed product proposal and retained delivery plan · 2026-10-09
- Corresponding Rosetta L2 row · 2026-10-09
Rosetta agent row.
Selected product correspondence. Circle occupies L2: what could justify this claim? It helps readers inspect attribution and disagreement; forecasts belong with ReFu and action proposals with Agentz.
- Product L2 · Epistemology
- Sourced observations and comparison
What could justify this claim? Circle makes the basis of an account inspectable through original sources, attribution, comparison and correction.
How the Rosetta agent row is used
Skyzai presents seven products: APU, Circle, ReFu, Agentz, Menexus, LIQUID and MurMur. Agentz is the continuing centre, with Cortex memory and Nexus connections. APU is the interface. Menexus means ensurance, insurance and assurance. Product roles preserve the underlying Rosetta coordinates. Emergentism is the framework across the whole. The Spectre network is a component within the wider Marketsphere programme; Permanent Composability supports independent reuse across the products.
The Rosetta agent row relates this product’s inquiry, reasoning and specialist skills to Emergentism. Several models, people or tools may contribute to the work. The philosophical correspondence, product responsibility and agent dispatch contract remain distinct; this page neither establishes deployed performance nor grants a model permission to act. This product direction does not migrate runtime contracts or amend signed source history.
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.