Murmur · Capital allocation engine
Put capital in context.
Useful personal offices. Independent perspectives. Collective intelligence. Murmur is designed to bring goals, obligations and permitted research into clearer capital decisions.
Concept illustration: separate comparison groups, not pooled funds or live portfolios.
Start with your own circumstances.
The intended personal office lives in Agentz: a place to review goals, assets, liabilities, commitments and possible actions. A useful plan starts with your circumstances, not a crowd average.
You can use the personal experience without contributing to collective research or joining an investment service. Your goals, time horizon, liquidity needs and limits remain explicit.
Let useful work inform a wider view.
Murmur’s collective intelligence is designed to emerge from separately permitted outputs across the connected apps.
- apu.bot investigates source material and alternatives.
- Circle contributes sourced observations and corrections.
- RealityFutures contributes scenarios, forecasts and uncertainty.
- Agentz prepares reviewable plans and proposals.
- Cortex preserves accepted records; Nexus scopes permitted context.
Comparable contributions belong in separate research groups, matched by goals, risk, horizon, mandate and other constraints. A household reserve and a leveraged trading strategy should not be blended into one answer. Shared sources, revisions and recycled signals must stay visible.
Using an app does not contribute your information automatically. Research needs a separate, purpose-bound choice, minimal data and defined correction and withdrawal handling. Agreement among contributors is not evidence of accuracy or investment performance.
Research, decisions and execution stay distinct.
The ambition is a capital system that combines useful personal planning, tested collective research and separately defined managed strategies. A managed service or investment vehicle would need its own accountable operator, mandate, costs, rights and exit arrangements.
Research participation does not pool your money or authorise trades. AI proposals do not sign or spend. Any execution requires a separate, valid mandate and the appropriate execution provider.
The current work is design and local synthetic testing. Live app integration, portfolio management, service economics and investment outcomes remain to be demonstrated. This page offers no account opening, investment subscription or order execution.
Direction and delivery · VMOSK-A
A proposed website plan for this product; a complete product charter and owner adoption remain open. Vision and mission set the direction; objectives, strategies, measures and skills make the work testable.
- Vision
- Capital decisions reflect the circumstances of the people they affect, with useful collective research available by choice.
- Mission
- Compare separately permitted contributions within compatible cohorts, preserving source ancestry, uncertainty and personal constraints.
- Objectives
- Define one consented research cohort, its evaluation, corrections and withdrawal handling before any managed strategy.
- Strategies
- Keep personal planning, research contribution, strategy selection and execution independently permissioned. Test usefulness against a simple baseline.
- Measures & triggers
- Proposed measures: permission fidelity, duplicate-source concentration, research calibration, withdrawal handling and total cost. Thresholds and baseline are unselected.
- Agents & skills
- Research design, permission/adapter engineering, independent evaluation and product ownership need assignment. Investment operators would be a separate role.
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.
- Inherited consumer direction at eef5c0d237eafc87558c77dddb0811a8f3ec9777—not an adopted charter · 2026-10-01
Distinct responsibilities.
Murmur has no selected Rosetta row in this page’s inspected source map. Its seventh catalogue position does not make it L7.
- Row placement
- Unselected in the inspected product map.
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.