Solum
Evidence + context assist
A spine for preserving sources, context, and the “why” behind conclusions.
Systems Map
Layer: System (Documentation)A reference hub: what exists, what each surface governs, and the boundaries between them. This page is orientation, not a funnel.
Parent framing
Scientia is the internal system doctrine that governs how truth, context, evidence, decisions, and execution are separated, composed, and audited. It is not a company, product, or platform—it is the epistemic and architectural frame.
Scientia.io is the runtime and interface layer that surfaces Scientia-aligned systems, engines, and lenses to humans. It does not own logic; it exposes systems without collapsing boundaries.
Structure
Scientia (system doctrine — internal)
→
Scientia.io (platform/runtime — interface layer)
→
Engines / internal layers
- RadixOS — Decision & Accountability
- Solum — Evidence & sources
- Pondus — Context engine
- Custos — Execution & workflow (no authority)
→
Lenses (Solum-powered; surfaced via Scientia.io)
- DropSignal
- HypeWatch
What this is
- A map of systems and boundaries (read-first orientation).
- A way to understand which surfaces are foundational vs situational.
- Not a roadmap.
- Not a product catalog.
Foundation systems
The constraints and operating surfaces that define the work.
RadixOS
Decision operating system
Ownership, judgment, and a record that survives hindsight.
Open →
Governance
Boundaries and review surfaces
Structure that keeps decisions reviewable and constraints real.
Open →
Field systems
Operational surfaces that run inside the constraints.
Custos
Execution & workflow layer (no authority)
An internal execution layer that structures workflow and handoff without replacing judgment.
Open →
Pondus
Internal orchestration layer
Internal engine used to coordinate work and operations.
(Not publicly accessible)
PennyWize
Legacy surface (deprecated)
(Replaced by Solum)
Relationships
RadixOS defines decision ownership and traceability.
Governance keeps boundaries and review rhythms explicit.
Solum preserves evidence and context that decisions depend on.
Custos structures execution workflows without creating authority.
What changes vs what doesn’t
Doesn’t change
- Decisions remain owned by humans.
- Context stays legible over time.
- Constraints stay explicit and reviewable.
Changes
- Which field surfaces are active for a given effort.
- What gets packaged vs kept internal.
- Which entry points are relevant for the current moment.
How to navigate
If you’re here for boundaries
Read how constraints are defined and upheld.
If you’re here for the spine
Start with decision ownership and traceability.
If you’re here for execution
See how work is packaged without changing the premise.
Entry points
Focused surfaces that sit inside the map.
DropSignal
A Solum lens for product drops with evidence and sources.
Open lens →
HypeWatch
Evidence-first trend observations without predictions.
Open lens →
Invariant Execution Kits
Studio deliverables (Custos-powered) that package workflows, templates, and handoffs.
View →
Operator Notes
Read-only operational logs: decisions, observations, postmortems.
Open →
Context links