Foundation
Principles that keep Murtek apps aligned.
Murtek products are built around a shared hierarchy: preserve meaning, show provenance, earn trust locally, and keep every app aligned with the same long-range causal reasoning mission.
Design hierarchy
Every app should make useful progress without weakening the suite.
The Foundation area explains how Murtek weighs usefulness, privacy, trust, and growth when product decisions point in different directions.
-
P0: Causality is the direction of travel
Murtek exists to help people understand how observations, behavior, environment, timing, and outcomes may relate. Early products can be educational or operational, but they should leave cleaner evidence for deeper reasoning later.
-
P1: Meaning must survive the interface
Labels, categories, timing, source, uncertainty, and user intent should remain portable across iPhone, web, future Android, APIs, and reference data.
-
P2: Provenance beats polish
Attractive interfaces matter, but claims are only useful when the source, limits, freshness, and transformation path can be understood.
-
P3: Local value comes first where trust is not ready
First-wave experiences should work without unnecessary accounts, cloud sync, payment prompts, or health-data collection unless those features are clearly offered and needed.
-
P4: Shared contracts come before app drift
When a pattern will recur across Murtek apps, it belongs in Foundation before one product quietly becomes the only source of truth.
-
P5: Operational evidence is part of the product
Public pages, support paths, clear labels, evidence trails, and recovery plans are part of the product. They help the suite stay understandable as it grows.
-
P6: Security and privacy bound the claim
Murtek avoids overclaiming. Public copy should be clear about current data handling, HIPAA status, account scope, and production safeguards.
-
P7: Growth must stay useful and honest
Search visibility, content cadence, social engagement, and public labels should help the right users find the right product state without pretending a preview is a finished clinical system.
Common glossary
Shared words reduce product drift.
Key Foundation terms include design principle, provenance, operational evidence, account prompt policy, responsible disclosure, and shared product boundaries.