Internal system · Public-safe case study

SUNNY

An owner-controlled AI-assisted operating system with governed workflows, deterministic checks and evidence-led execution.

  • AI systems
  • Governance
  • Local-first architecture
  • Tooling
  • QA

Challenge

Build an AI-assisted operating system that can help with research, planning and checks without taking over authority, inventing certainty or mixing private systems into public claims.

Goal

Help the operator understand the work, retrieve approved knowledge, run repeatable checks and keep evidence attached to decisions.

Scope

What the work covers.

  • 01Local-first conversation and voice
  • 02Controlled tool integrations
  • 03Explicit approval before consequential actions
  • 04Business-state awareness
  • 05Knowledge retrieval
  • 06Desktop and paired-device interfaces

Approach

Structure before surface.

Approved business and project sources remain the source of truth. Models can propose and assist. Scope, audit trails and failure handling decide what is allowed to happen next.

Design

A visual reason for every choice.

A calm digital-office interface shows status, evidence and the next action instead of burying the operator in internal machinery.

Engineering

Built for the real path.

Typed local services, explicit capability boundaries, one-time approval receipts, project isolation, secure credential references and evidence-led runtime checks.

Key decisions

Constraints became part of the design.

  1. 01

    Retrieved content cannot approve work

  2. 02

    Private integrations do not silently become long-term memory

  3. 03

    No connector can grant itself access

  4. 04

    External outcomes stay unverified until they are reconciled

Result / deliverable

An active internal system that supports Sunlit Logic’s delivery workflow. It is still developing, and unfinished capabilities are not presented as proven public products.

Stack / system

Python · SQLite · Local model routing · Typed policies · macOS application · Paired-device interface

What was verified
  • Controlled execution paths
  • Project isolation
  • Credential boundaries
  • Read-only retrieval behavior
  • Failure and replay controls

Start here

Want to turn your own problem into a working product?

No technical specification required. Tell us what should be different when the work is done.

Start a project