Start something, or return to a Matter.
Your questions, Shadow’s responses and the work they lead to stay together here.
Pull useful objects forward, compare them, swap them, and keep talking from the same Matter.
Pull an image or result forward. Your next expression can continue from it.
Open a turn to see its source and continuity.
Your current Matter stays attached.
Current activity and what needs your attention.
Open the detail you need. Return to the same Matter.
Connect to open your saved conversations and continue working.
Shadow is ready.
Start with the thing you want done. Shadow keeps the Matter together, reaches the services you allow, and shows the work as it moves.
Live Shadow
The public site remains useful without pairing. A paired browser reads a minimized projection directly from Shadow on this device. Provider identities, raw security graph data, IP/MAC data and private evidence are excluded from the browser projection.
127.0.0.1 only after local pairing. Railway continues to handle encrypted inbound expressions; it does not receive this workspace projection.
Your own expressions stay visible across Shadow surfaces. Uncertainty is shown as one field inside the feed, not as the whole experience.
Once paired, your exact recent request will appear here.
Choose a question to navigate Shadow's current state without turning the interface into an architecture dashboard.
No current activity loaded.
No recent feed loaded.
Capture preserves your exact expression first. The browser does not decide the Matter, provider, model or authority. Optional hints only change where Shadow looks first.
Continue in Shadow to reveal current Matter state.
A calm view of the Matters, sessions, devices, environments, teams and providers Shadow is coordinating.
Pair Shadow to reveal bounded current state.
A calm view of what is current, degraded, unknown, waiting, recoverable and still unfinished.
Continue in Shadow to load the operational ledger.
No activity loaded.
Shadow will show satisfaction, continuation, exposure and cleanup here.
Receipt understanding has not been validated by the user.
No detailed receipt loaded.
Local Security state remains private.
Model/provider state not loaded.
Provider identities are never shown here.
Discovery and media routes not loaded.
Isolation state not loaded.
Shared coordination state not loaded.
Lineage, curation, source-governance and recovery state not loaded.
Surface state not loaded.
Continue in Shadow to read current privacy transport state.
Continue in Shadow to read controlled capability coverage.
The workspace
Shadow is intended to let you work inside the Matter while Activity, Security, capabilities, sources and background work stay attached to it.
Continue from the selected Matter instead of rebuilding context every time.
See what is working, waiting, blocked, verifying, recovering or complete.
See posture, access, currentness, Control Map and defensive boundaries in consequence-first language.
Deliberately open the wider capability field when the Matter needs more depth.
Explore without surrendering the choice
A large option space stays visible as an option space. Shadow should not silently turn thousands of legitimate possibilities into a tiny personalised feed.
Continuity
Shadow keeps dependencies, expected events, currentness and unresolved work attached to the Matter. It should continue legitimate read/prepare work when already permitted, wait when it must, and involve you when the decision genuinely belongs to you.
A new question or correction recomputes the Matter; it does not silently orphan valid work that was already underway.
Expected events and blocked work retain their unlock condition instead of relying on you to remember to ask again.
Conversation, context, authority and evidence return to the same Matter across interruption and supported surfaces.
Provider, device and service state can be current, stale, unknown or unavailable. Connection never becomes automatic permission to act.
A branch can investigate an alternative without silently replacing the root Matter. Return paths, unresolved dependencies and surviving work stay visible.
If a source, assumption or instruction changes, Shadow identifies dependent work that may now be stale instead of leaving old answers looking current.
Observed fact, interpretation, derived material and curated sources remain distinguishable. Keeping something for reuse does not make it verified, canonical or authorised.
Capacity, uncertainty, elasticity and reserve constrain Honest Commitment. Trust is accumulated evidence, not a permission token or hidden score.
Operational legibility
Shadow should expose the chain at the level that matters to you, with deeper technical detail available on demand.
All Shadow
Earlier capability work is not meant to vanish when the interface gets simpler. It composes underneath the Matter and remains inspectable.
Reasoning, source recovery, uncertainty handling, comparison and external intelligence can be brought into the Matter without turning a provider into Shadow.
Shadow can expose posture, changes, sessions, permissions, network evidence and defensive options here. Browser-visible control stays separate from device enforcement: RADAR and Mesh can use admitted observations, SHIELD and Lockdown can govern Shadow/provider state, exposure minimisation preserves the old STEALTH purpose without claiming invisibility, and Self-Access & Permission Audit shows what Shadow itself can currently reach. Radio, installed-app and deeper device controls require native or managed-platform capability. Red Team remains bounded owned/authorised falsification, not offensive autonomy. Safe Session / Airlock remains the isolated path for risky work when its enforcement boundary is actually proven.
Work moves through explicit ownership, capacity, handoff, checkpoint, recovery and return rather than disappearing into an invisible agent loop.
Read, search, availability, summarisation and preparation can be coordinated from the web when the provider route is admitted. Sending, calendar mutation, device-local contacts and home/device effects remain separate authority and capability boundaries. Current, stale and unknown are never collapsed into one “connected” state.
Shadow keeps the Matter coherent across interruption. Legitimate read/prepare work can continue within current authority; new consequential authority is never inferred from absence, silence or reconnection.
Discovery preserves the difference between eligibility, exposure, ranking, recommendation, decision, authority and effect. A viewing window is not automatically a ranking.
Upload or reference files, images, video, sites and APKs for bounded inspection, provenance and contradiction work. Personal media/site catalogues stay attached to the Matter. Device-installed app state, quarantine and local gallery/camera access require native capability rather than being faked by the browser.
The same Matter can move, mirror, extend or resume across supported surfaces without treating a new device or chat as a new work identity.
One Shadow · different execution surfaces
A capability stays in the same Matter even when sensing, reasoning or effects run somewhere else. Shadow should expose the actual execution surface instead of turning platform limits into missing product capability.
Matter, reasoning, Connected Life, Explore/Learn, security posture, evidence, media, approvals, history, recovery and routing can be presented and coordinated here.
Provider adapters, currentness, evidence acquisition, reasoning routes, receipts and server-side defensive controls run behind the workspace when separately admitted.
Android/iOS add local sensors, stronger device identity, radio state, installed-app inspection, offline continuity and OS effects that a normal browser cannot honestly claim.
Risky or sensitive work moves into a bounded isolation path only when its actual network, credential, filesystem, media and cleanup enforcement is proven.
Privacy transport
Shadow's Tor/Onion work remains part of the design. The current production website uses direct HTTPS; it does not currently claim Tor transport. A stricter mode must alter actual network behaviour and fail closed where required.
Reduce context and disclosure before a remote provider is used. This can apply whether transport is direct or Tor-routed.
Use Tor where the operation supports it. Any non-Tor fallback must be allowed by policy and visible rather than silently substituted.
No silent clearnet fallback. If the route is unavailable, capability waits, degrades locally or asks you before privacy is reduced.
Where Shadow controls both ends, a future .onion endpoint can avoid the exit-relay leg and give the user a Tor-native Shadow route.
Some Matters should remain local or deliberately disconnected when external routing is unnecessary or incompatible with the privacy boundary.
For hostile or sensitive sources, transport privacy can compose with Safe Session instead of treating Tor alone as endpoint safety.
Secure execution environment
Dark Web is the first profile. Shadow separates control, verification, the disposable session and Tor egress. This Web surface can assess and prepare the boundary; it does not claim that isolation or Tor enforcement exists until the underlying runtime proves it.
The website can show the required boundary and current evidence. It cannot manufacture isolation from browser UI alone.
Current live route
The current web path can preserve your exact expression, verify the ingress record, encrypt the expression for your Shadow device and queue it to the local Shadow route.
That transport is live. A model is not automatically contacted, and protected actions are not automatically authorised. Those capabilities join only when their own gates are satisfied.
No Shadow trace yet.
Truthful current state
Open a node, zoom into what it means, then keep working without leaving the Matter.
Create a Matter, keep its work and context attached, and return without rebuilding it.
Shadow keeps the expression, Matter and work path together. Choosing a node changes where Shadow looks, not your authority.
New browser-originated work is paused. Your Matter is preserved.