Menexus · Vision

Menexus

Face uncertainty with dependable preparation, explicit protection and evidence you can inspect.

Product design in development. Insurance depends on actual providers and agreed terms.

Preparation, protection and inspection · concept illustration, not coverage or a live service

Mission

Connect ensurance, insurance and assurance to the risks and possible futures people need to manage.

One of Skyzai’s seven product strategies, designed to contribute to outcomes for Me (individuals), We (organisations) and They (machine intelligence).

Rosetta agent row · Cosmology

What large-scale structure is being modelled?

Menexus examines the system around a commitment: dependencies, providers, risks, protection and evidence of delivery.

Objectives

Clarify the commitment and the risks around it.
Make protection terms, exclusions and responsibility understandable.
Check results and preserve unresolved claims or disputes.

Strategy

Ensurance plans and recovery measures; proposed insurance against specified risks; assurance through evidence, verification and outcome records.

Ensurance

Prepare for dependable delivery, prevention and recovery.

Insurance

Consider protection against specified risks with named providers and explicit terms.

Assurance

Inspect commitments and outcomes against the evidence.

KPIs

Proposed measures of progress

Measure commitment outcomes, prevention and recovery effectiveness, comprehension of protection terms, unresolved disputes and evidence completeness.

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.

Commitment readiness · definition and limits

Eligible population: All service commitments submitted for agreement in the review month, including refused or incomplete proposals.
Calculation and units: Proposals with provider, responsible parties, versioned deliverable, deadline, criteria, permitted inputs and remedy recorded / all submitted proposals. Report missing required fields individually.
Observation period: Calendar month, with a dated submission cutoff; revisions retain the original proposal identity.
Evidence source: Versioned proposal register and criterion-level completeness review.
Accountable role: Commitment-quality reviewer; actual appointment not recorded.
Limitations: Complete terms do not establish consent, provider capability or authority. Declined proposals remain declined, not fulfilled.
Observation: Not recorded
Target: Unset

Accepted due commitments · definition and limits

Eligible population: All agreed commitments due during the month under the pinned agreement version.
Calculation and units: Due commitments with every mandatory criterion met, complete evidence, independent criterion review and explicit customer acceptance / all commitments due. Separately report pending, partial, failed, disputed, overdue and cancelled cases; cancellations are not successes.
Observation period: Calendar month, evaluated at the declared review cutoff. Late acceptance is reported separately.
Evidence source: Pinned agreement, deliverable revision, reviewer findings and attributable customer decision.
Accountable role: Service-outcome reviewer independent of the provider; appointment not recorded.
Limitations: Acceptance is distinct from business benefit and payment. Do not drop disputed or failed commitments from the denominator.
Observation: Not recorded
Target: Unset

Acceptance evidence completeness · definition and limits

Eligible population: Every required criterion/evidence pair in commitments reviewed during the month.
Calculation and units: Required pairs with attributable, accessible and version-matched evidence / all required pairs. Show each critical missing item alongside the ratio.
Observation period: Calendar month; snapshot at each review and preserve later corrections separately.
Evidence source: Criterion/evidence register, source availability and revision history.
Accountable role: Evidence-quality reviewer; appointment not recorded.
Limitations: Complete evidence may demonstrate a failed criterion. A high aggregate score cannot conceal a mandatory gap or substitute for independent review.
Observation: Not recorded
Target: Unset

Protection understanding · definition and limits

Eligible population: All eligible reviews of an actual insurance proposal opened during the month; eligibility is declared before collection.
Calculation and units: Reviews correctly identifying provider, covered risk, exclusions, cost, claims process and proposal-versus-policy status / all eligible reviews opened. Report incomplete reviews separately.
Observation period: Calendar month; assessment before accepting any protection proposal.
Evidence source: Versioned provider terms and separately consented comprehension assessment; no visitor responses are collected here.
Accountable role: Protection-review lead, with qualified provider input; appointments not recorded.
Limitations: Non-insurance cases are excluded explicitly. Understanding terms establishes neither qualification, policy issuance nor a payable claim.
Observation: Not recorded
Target: Unset

Unresolved discrepancy age · definition and limits

Eligible population: All open discrepancies at month end, including reopened disputes.
Calculation and units: Open count, median age and oldest age in days since first attributable notice. No ratio denominator; show overdue responses separately.
Observation period: Month-end snapshot; retain initial notice and reopening dates.
Evidence source: Discrepancy register, response deadlines and preserved dispute history.
Accountable role: Remedy coordinator accountable to the parties; appointment not recorded.
Limitations: Closing a ticket is not evidence that a remedy worked. An empty population has no median; it is not a measured zero-day resolution.
Observation: Not recorded
Target: Unset

Accepted remedies · definition and limits

Eligible population: All agreed remedies whose independent review and declared follow-up are due during the month.
Calculation and units: Due remedies with every mandatory corrective criterion met, complete corrective evidence, fresh independent review and explicit customer acceptance / all remedies due. Report partial results, refusals, overdue responses, reopened disputes and pending follow-up.
Observation period: Calendar month using the follow-up window agreed before collection.
Evidence source: Original discrepancy, remedy terms, corrected revision, fresh review and customer acceptance.
Accountable role: Independent remedy-outcome reviewer; appointment not recorded.
Limitations: A rework proposal is not completed correction; a proposed refund is not settled money. Prevention effectiveness requires separate causal evidence.
Observation: Not recorded
Target: Unset

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 · 18 October 2026. 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 L5 · Cosmology

Responsibility. Ensurance, insurance and assurance

Reasoning approach. Systematic reasoning: map dependencies and failure paths, compare testimony with available evidence and check how preparation, protection and recovery fit together.

Commitment planner

Skills and responsibilities. Defines the work, accountable provider, acceptance criteria and response when something goes wrong.

Input. The permitted brief, dependencies, responsible parties and proposed terms.

Output. A versioned commitment, preparation checklist and proposed remedy with a responsible party and response deadline.

Limit. Cannot bind the parties, accept delivery or settle a dispute. A remedy coordinator follows notices and escalation under the agreed terms.

Protection analyst

Skills and responsibilities. Compares coverage, exclusions, cost and claims handling. Actual cover requires a qualified provider and an agreed policy.

Input. The declared risk and attributable, versioned provider terms.

Output. A comparison of protection terms, unanswered questions and provider/policy qualification gaps.

Limit. Cannot issue cover, establish eligibility or promise claim payment. Qualified insurance operation requires actual appointments, applicable mandates and provider-issued evidence.

Evidence reviewer

Skills and responsibilities. Checks what was delivered, records uncertainty and keeps disputes available for review.

Input. Pinned criteria, the delivered revision, attributable evidence and any original discrepancy.

Output. Criterion-level met, failed or unresolved findings, followed by a fresh correction review where needed.

Limit. Cannot independently approve its own work, accept on the customer’s behalf without an actual mandate, authorize payment or equate complete records with a successful outcome.

Required skills include risk analysis, insurance design and qualified operation, domain verification, evidence review, service delivery and independent assessment; the page does not establish those appointments.

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.

A more dependable piece of work.

Illustrative case · Help our team choose and commission an analysis within our budget.

Make a commitment easier to rely on.

Before commissioning the analysis, the team needs to know what dependable delivery would mean.

Prepare: Name the work, responsible provider, deadline and acceptance criteria.
Protect: Inspect failure handling, remedies and any separately contracted protection.
Verify: Check delivery and useful outcomes against the agreed criteria; keep disputes visible.

A fictional example of the intended experience. No request is sent, personal memory stored or money moved.

Revisit the assumptions with ReFu

Local demonstration · fictional people and records. Choose a state to inspect it. These controls do not agree terms, accept work, submit a claim, retain personal data or move money. Reloading resets this page.

A workshop commissions independent analysis.

The workshop wants to compare ways to restore its inspection capability. This is the analysis case used across the product pages; it is separate from the actuator purchase and any later customer inspection service.

Ensurance · prepare the commitment

Record: ANALYSIS-01 · agreement v1
Customer: Maya, the workshop’s designated customer representative (fictional)
Provider: Harbour Analysis Studio, responsible for the analysis and agreed rework (fictional)
Deliverable: A decision brief comparing repair, replacement and an inspection service; a dated source appendix; and an assumptions sheet.
Timing: 28 October 2026, 18:00 UTC; customer review by 30 October.
Responsibilities: The customer supplies the permitted brief and names the accepting representative. The provider supplies the analysis and responds to discrepancies. Sam checks the criteria; Maya records the customer’s decision.
Preparation: Confirm source access, scope and review availability before agreement. Identify missing information early; changes to scope, price or deadline require a separately accepted revision.
Agreed remedy design: For a material omission, request rework within two working days of notice, followed by fresh independent review. If rework is refused or disputed, use the agreed escalation contact. Any cancellation, refund or settlement needs separate agreement and evidence.
Escalation contact and response: Lee, the jointly designated service liaison (fictional), receives both accounts and acknowledges a notice within one working day. Lee coordinates a response within three working days. If the parties still disagree, the discrepancy stays open for their agreed dispute process; Lee cannot impose settlement.

These are proposed terms in the preparation state. Only the agreed-case snapshots record fictional acceptance of those terms; a designated role alone supplies no actual mandate.

Prepare the commitment

Inspect the proposed terms before either party commits.

Agreement: proposed · v1
Required files: Incomplete · 0 of 3
Review: Not recorded
Delivery acceptance: Not applicable · no agreed service
Later workshop outcome: Not recorded
Payment: Not recorded

Assurance · inspect each criterion

unresolved. Compare all three alternatives against the workshop’s stated need.
unresolved. Attribute material claims to dated, inspectable sources.
unresolved. Separate assumptions, costs and uncertainty from observed facts.

Files present does not mean criteria met. An independent finding does not accept work for the customer. Accepted analysis does not prove that the workshop’s later decision succeeded.

Response and remedy

Proposed rework and escalation terms await agreement.

Inspect the retained history · 1 records

A draft is ready for the customer and provider to inspect.

Insurance · separately qualify protection

No coverage established. No qualified insurer, accepted policy or payable claim is recorded in any state of this case. Rework under a service agreement is distinct from insurance.

Prepare. Protect. Verify.

Starts with: Explicit commitments, Reality Futures scenarios, risk terms and attributable evidence.
Produces: Inspectable preparation plans, proposed protection terms and assurance records, each with its own acceptance and operating requirements.

This is product direction, not an issued insurance policy, coverage promise or live insurance service. Legal-person responsibilities, providers, terms and acceptance must be established for each offering.

Reality Futures explores what could happen. Menexus asks how to prepare, what protection is appropriate and how the outcome can be verified. Menexus GmbH retains its separate legal identity and responsibilities.

Three responsibilities. One risk-aware case.

Ensurance · make commitments dependable

Preparation, prevention, fulfilment and recovery: identify what needs to happen and the evidence that would show it has.

Insurance · define protection against specified risks

Explore explicit coverage terms, providers, exclusions and claims procedures. An illustration or forecast creates no policy or promise of payment.

Assurance · inspect the evidence

Check commitments and outcomes against declared criteria, record uncertainty and disputes, and feed corrections back into the shared case.

Connections through Agentz

Nexus belongs within Agentz and governs purpose-limited context. Access to a case is limited to its declared purpose and does not grant authority to act.

Memory through Agentz

Cortex and redundant memory belong within Agentz. Menexus uses permitted case records; it does not own the shared memory layer.

Your interface through APU

APU is the voice, text and navigation interface. It presents the permitted case so you can inspect commitments, protection terms and evidence.

A Menexus plan, with its own delivery gates

The six-field outline below proposes Menexus delivery work from the October 13 product direction. The October 17 Flutter review bounds current implementation claims; it is not an accepted insurance delivery plan. The older Cortex plan describes Agentz memory and does not define Menexus insurance work.

Capabilities and current proof.

As reviewed on 2026-10-17, 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.

Ensurance preparation · Proposed
Menexus currently owns preparation for obligations and risk responses.
Current limit: No qualified contract, operator or delivered ensurance service is established.
Insurance terms and claims · Proposed
Menexus currently owns specified protection and insurance semantics.
Current limit: The local legacy case receipt is not a policy, underwriting decision, coverage, claim or regulated operating authority.
Assurance verification · Proposed
Menexus currently owns evidence that commitments were fulfilled.
Current limit: The historical menexus-core carrier returns PROPOSED case snapshots; it does not assure performance.

Inspect the full capability record and source references

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: People and organisations can meet commitments and face uncertainty with dependable preparation, explicit protection and inspectable evidence.
Mission: Connect ensurance, insurance and assurance to the risks and possible futures people need to manage.
Objectives: Clarify commitments and risks, compare protection terms, preserve evidence and make failures, exclusions and disputes visible.
Strategies: Ensurance plans and recovery measures; proposed insurance against specified risks; assurance through evidence, verification and outcome records.
Measures & triggers: Measure commitment outcomes, prevention and recovery effectiveness, comprehension of protection terms, unresolved disputes and evidence completeness.
Agents & skills: Required skills include risk analysis, insurance design and qualified operation, domain verification, evidence review, service delivery and independent assessment; the page does not establish those appointments.

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.

Define each offering, eligible provider, terms, evidence, exclusions, dispute process and operating responsibility before making a coverage or service claim.
Establish purpose-limited access to Agentz case records and the APU interface without conflating context access, service acceptance and transaction authority. Product direction is not an adopted charter or a completed runtime integration.
The retained October 9 Cortex VMOSK-A describes Agentz memory and cannot serve as a Menexus insurance delivery plan. The six-field outline here needs its own accepted scope, qualified provider and evidence gates.

These working documents require access to the corresponding private GitHub repositories.

Adopted owner product direction · 2026-10-13
Current Flutter function and Menexus boundary review · 2026-10-17
Corresponding Rosetta L5 row · 2026-10-09

Rosetta agent row.

Selected product correspondence. Menexus retains the L5 public product home. Ensurance, insurance and assurance are its product direction; Cortex and Nexus now belong within Agentz. Existing functional coordinates and compatibility IDs retain their meaning.

Product L5 · Cosmology: Ensurance, insurance and assurance
What large-scale structure is being modelled? Menexus examines the system around a commitment: dependencies, providers, risks, protection and evidence of delivery.

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.

Availability and boundaries

These are intended offerings. The interactive case is a local demonstration, separate from Flutter integration, an operating service and qualified insurance. Insurance terms, qualified operators, contractual responsibilities and live service availability must be established separately.

Use Menexus where a commitment needs preparation, evidence or remedy. The products are optional contributors, not compulsory steps.

Return to Me Return to We Return to They

Revisit the assumptions Continue with Agentz Inspect the separate actuator case