Choose a technical, team, human or optional symbolic/personal entry. Everything on this page runs in your browser: no account, no B1 job, no database write. The point is to show how MetaCore keeps data, assumptions, symbolic models and authority boundaries separate before any private AI treatment is allowed.
● Browser-local · personal data stays on this page · 0 runtime API calls
4 entry modes10 local instruments6 guided experiments3 static JSON endpoints0 private runtime callsOFF live gateway
START HEREPick one path. You do not need to read the whole Lab.Run a ~60 second guided experiment, or jump straight to the context mode that matches your question.
Enter only what you want to test. Birth date and city stay in this browser. If birth time is unknown, MetaCore marks 12:00 as an assumption instead of pretending it is a fact. The symbolic matrix is reflection only: not evidence, not psychometric assessment, and not a basis for high-stakes decisions.
LOCAL ONLYno fetchno storageno cookies
This demo does not geocode the city and does not calculate a live natal chart. Exact houses / Ascendant stay blocked when time is assumed.
NEXT LAYER · NOT CALLED YETWhat could MetaCore add after this?City/timezone resolution · astronomical positions · temporal cycles · a richer context profile · live AI treatment.
Adapted from MetaCore Love's public trigger-map pattern. The demo organizes what you report; it does not infer attachment style, pathology, partner intent or relationship prognosis.
No label. No diagnosis.Only a structural map of the self-reported loop.
POST /demo/v1/human/loop-map · LOCAL
{\n "status": "WAITING_FOR_LOCAL_INPUT"\n}
TEAM CONTEXT · OPERATIONS
Profile the mechanism, not the employee.
Adapted from Networker's public TeamWorker pattern. Four coarse operational signals expose where work is sticking without turning the result into HR scoring.
Not HR assessment. Not employee profiling. Safety/harassment/threat language stops routine optimization.
Operations before psychology.Decision · ownership · communication · rhythm.
POST /demo/v1/team/friction · LOCAL
{\n "status": "WAITING_FOR_LOCAL_INPUT"\n}
TECHNICAL MODE · ONE OPERATING CHAIN
Five instruments. Five different questions.
Read them as a sequence: orient the knowledge domain, compile the relevant context, expose the state change, classify the evidence, then check who may act.
PUBLIC LIBRARY MAP
Knowledge Topology Navigator
Ask a cross-domain question. The map suggests where to look — and keeps each region's epistemic class visible. It does not answer the question for you.
POST /demo/v1/knowledge/route · LOCALorientation ≠ proof
Context Compiler
Public demo of the Profile Context principle: Signal × Relevance × Confidence × Timing × Human Context.
Each signal: strength · relevance · source confidence · timing · human context
POST /demo/v1/context/compile · LOCAL
State DELTA
Make continuity visible. Compare two state objects; nothing is written back automatically.
Spatial QA preset: shows a candidate moving from an unresolved collision to READY_FOR_HUMAN_QA. It demonstrates state continuity only — no mesh is loaded, no geometry solver runs, and nothing is promoted to production.
POST /demo/v1/state/delta · LOCAL
Epistemic Router
Force a claim to declare what kind of knowledge it actually is.