Sightbase is a local-first, personally controlled, structured knowledge and data substrate that:
- Lives on our own hardware
- Is reachable across devices (home, work, mobile)
- Acts as a source of truth rather than a cloud mirror
- Integrates databases, structured knowledge, and operational workflows
- Prioritizes visibility, ownership, and durability over convenience
Project Ipsum (Infrastructure Layer)
is the foundational infrastructure initiative of the SightBase: a deliberately owned, privately operated, and globally reachable data node built on personal hardware. Its purpose is simple and uncompromising—to establish real, independent computational ground outside third-party cloud platforms, while retaining full remote accessibility and operational control. At its core, Project Ipsum converts a physical home machine into a live, production-grade SQL Server that can be securely accessed from phone, tablet, and office laptop anywhere on the internet. Nothing is rented. Nothing is abstracted away. Hardware, operating system, database engine, network exposure, and authentication boundaries are all explicitly configured and understood.
Project Ipsum is not an experiment.
It is infrastructure.
Device Mesh (Access Layer)
Purpose:
To eliminate the concept of “this machine vs that machine.”
Devices involved:
- Home servers (IPSUM → MEGA)
- Work laptop
- Personal laptop (Defiant)
- iPad (Renaissance)
- Phone
Function:
- Each device is a lens, not a silo
- No device owns data; all devices observe and act upon the same core
- Failure or absence of one device does not break the system
Database Core (Memory & Truth Layer)
Purpose:
To act as the authoritative record of:
- Workflows
- Processes
- Financial systems
- Conceptual models
- Historical states
Characteristics:
- SQL Server–centric
- Explicit schemas
- No hidden logic
- No “spreadsheet truth”
This is the system’s memory. If it is not here, it is not real.
Process Encoding (Operational Layer)
Purpose:
To convert lived workflows into executable, inspectable structures.
Examples already in scope:
- Daily Cash Flow
- Accounting close
- Forecast logic
- Reconciliation steps
- Decision dependencies
Key rule:
Processes are no longer tribal knowledge.
They are mapped, named, stored, and replayable.
Cognitive & Conceptual Models (Meaning Layer)
Purpose:
To ensure the system is not just functional, but intelligible.
Includes:
- Logos / Theos duality
- Path to Value (Choice → Perspective → … → Value)
- Binary decision framing
- Recursive structure models
These models ensure that:
- Data aligns with meaning
- Actions align with intent
- Complexity remains navigable