Working thesis · Gate 0

Your company software should feel owned.

Trellis is a proposed AI operator for the open-source software of a small company: it manages the applications, reshapes them around the work, and acts across their content under one governed model.

First payload
Plane only
Current state
Not deployed
Control
Human-gated
founder intent

“Set up and run the software for my small company.”

one operating model
  • identity
  • authority
  • causality
  • receipts
01managehealth · backup · restore
02customizepreview · approve · reverse
03operateread · draft · change

Applications keep their records. Trellis keeps the operating contract.

The pain

The problem is not choosing another app. It is inheriting another system to babysit.

Conventional SaaS makes the first hour easy and every later change vendor-shaped. Self-hosting gives control back, then hands you installation, credentials, upgrades, backups, recovery, and integration work.

The invariant

Three jobs. One product.

If one plane is missing, this becomes an adjacent product—not Trellis.

01 lifecycle

Manage the software

Select only what the company needs. Provision it, observe it, update it, back it up, restore it, and retire it with evidence.

  • Declared versions and resources
  • Health, cost, drift, and recovery
  • Direct infrastructure ownership
02 change

Customize the software

Ask for fields, views, workflows, permissions, templates, or code changes without hiding the migration or the way back.

  • Versioned proposal and preview
  • Validation and human authority
  • Observed apply and rollback
03 work

Operate the company

Let a human or local agent work with messages, customers, tasks, documents, code, and environments through typed actions.

  • Stable identity and provenance
  • Bounded agent capabilities
  • Durable action receipts

Plane Steward · proposed v0.1

One real application first.

The first useful version does not install a fantasy company suite. It adopts one existing Plane service and makes one real project easier to create, feed to a coding agent, customize, observe, recover, and export.

  • Should reduce repeated project setup and context handoff
  • Must test lifecycle, customization, and operations together
  • Should establish the adapter contract for the next application
  • Does not yet replace Slack, email, CRM, or documents
Open Plane Steward
founder journeyone project
  1. 01
    AdoptObserve the existing Plane service without changing it.
  2. 02
    DeclarePut desired project state in a reviewable profile.
  3. 03
    WorkHand a bounded issue packet to a local coding agent.
  4. 04
    ReshapePreview and approve one visible Plane customization.
  5. 05
    RecoverRestore and export instead of trusting a backup badge.

The shared model

AI proposes. Deterministic code decides and records.

A model can interpret intent and assemble a plan. Identity, filtering, policy, approval, idempotency, execution, and receipts stay enforceable without trusting model prose.

See what is proven and what is not
example action receiptproposed
Illustrative · no Plane action occurred
intent
add customer priority to work
capability
work.configure_field
target
plane / studio-project
authority
candidate / reversible
acceptance target
observable · receipt generated only after live proof

Sovereignty, made testable

Control is a recovery exercise, not a flag in the footer.

For the first proof, sovereignty means declared regions and dependencies, open-source payloads, scoped credentials, exportable records, and a clean recovery path. It does not yet mean a fully EU-owned supply chain or zero external services.

Read the ownership contract

The build order

Make one app boring to own.
Then earn the right to add another.