Chromatic Ventures · Calgary · AI operations

An AI operating system for your business.

Chromatic Ventures designs, builds and hands over the agent infrastructure that lets a small team operate like a larger one: defined roles, written rules, a decision record, and verification that catches errors before they reach a client. Built first to run Chromatic’s own software company. Now built for yours.

Request a proposal See how it works

A reply within two business days. No sales call unless you want one.

  • 0
    lines of Swift shipped on the system
  • 0
    files in one native iOS product
  • 0
    months running in production
  • 0
    accessibility violations held
  • 0
    taxonomy entries structured
  • 0
    client engagements underway

Services

Most AI adoption stops at faster typing. The value is in the layer underneath: an operating system.

Defined agent roles with written operating rules. A decision record that survives staff changes and stops the same argument recurring. Verification layers that catch confident errors before they reach a client. Change control that determines what a machine may alter without sign-off.

Chromatic built this to run its own software company, and it has been through enough real conditions to be hardened rather than theoretical. Every engagement ends with documentation and a handover, so the system is yours to run.

Core engagement · fixed scope · six to eight weeks

AI operating system: design and build

An agent architecture mapped to your actual work. Written operating rules for each role. A decision record that survives turnover. Verification layers before anything reaches a client. A handover so your team maintains it without Chromatic.

  • Agent roles sized to the work, each with versioned operating rules
  • A decision ledger with formal supersession rules
  • A reconciliation layer for conflicting sources of truth
  • Scheduled review agents that report what changed overnight
  • Change control: what the system may alter without sign-off
  • Documentation, training and handover

For solo professionals and small agencies at capacity; founders keeping headcount low; consultancies whose clients are asking about AI.

Request a proposal

Product

Concept to shipped product

For founders with an idea and no engineering team. Product, design and implementation in one place — no three vendors and no translation layer. Chromatic has taken a native iOS product from nothing to store build on this system.

Fractional technical lead, or a scoped build with milestones.

Websites

Websites built as systems

Positioning, copy, design, build, measurement and the lifecycle behind the form — delivered end to end, in code you control. This site is the sample.

Two rebuilds currently underway, with operational agents in scope.

Structure

Taxonomy and information architecture

For teams building a classification system, a design system or a structured content model. Chromatic has built a 300-term taxonomy on a perceptually uniform coordinate system with its relationships preserved — the same discipline, applied to your domain. A narrow service, offered deliberately.

How an engagement runs

Six to eight weeks, in five steps.

Week 1DiscoveryMap how the work actually happens today. Name what stays human.
Week 2DesignRoles, operating rules, the decision record, and where verification sits.
Weeks 3–5BuildAgents, ledger, reconciliation, review schedules — against your real work.
Week 6VerifyRun it under real conditions. Fix what fails. Decide what it may do unsupervised.
Weeks 6–8HandoverDocumentation, training, change control. It is yours to run.
Fixed-scope buildThe core engagement. Quoted after discovery, not as a day rate. Starting price to be confirmed.
Fractional technical leadMonthly, for founders shipping a product without an engineering team.
Website systemFixed scope. Positioning through launch, with measurement and lifecycle included.

How it works

One operation in. As many roles as the work needs.

Not prompt engineering — organisational design applied to non-human collaborators. Each role has written rules: what it may read, propose and change. Chromatic’s own configuration runs six today; yours is sized to your work.

Example configuration — Chromatic’s own operation. Role names illustrative.

ArchitectOwns structure. May propose; may not merge.
BuilderImplements ratified decisions only.
ReviewerRuns nightly over the whole corpus. Reports drift.
ReconcilerResolves contradictions between sources of truth.
VerifierNo carried-forward claim without primary source.
LedgerRecords, supersedes, never deletes.

The decision record

Every decision is recorded with what it supersedes, and why.

This is what stops the same argument recurring after a staff change, and what lets a new person — or a new model — pick up the work without re-litigating it.

ledger/decisions.jsonl · D-057
D-041Feature excluded from the public buildSuperseded
R-012No carried-forward claim without re-verificationStanding rule
G-003Restoration guard and promotion ledgerActive

Reconstructed from real entries. IDs and dates are placeholders until the export is connected.

Safeguards

Each safeguard in the system exists because of a real condition it met. Four of them, and where they came from.

01 · runtime channel check

When the written rule and the running code diverge

A rule excluded a feature from the public build. The code did not: a flag returned true unconditionally, so every release build would have shipped it. The fix reads the build channel at runtime and fails closed on anything unknown, so the rule holds without anyone remembering to flip a switch.

What it means for youPolicy and implementation drift apart in every business. The system checks for it rather than assuming it away.
02 · re-verification rule

When an automated report restates something that never happened

A daily review restated two items from an earlier report — a filing made, an email sent. Neither had occurred. Both were caught by reading the source rather than the summary. The standing rule since: no claim is carried forward without re-verification against primary source.

What it means for youAutomated systems repeat their own errors until they harden into accepted fact. Verification has to be designed in, not added after.
03 · promotion ledger

When the system invents a record

The system generated entries for items that did not exist and propagated them. Deleting them was not enough. A guard now prevents their restoration, and a promotion ledger governs what may enter the canonical record and by what process.

What it means for youChange control is usually built after something ships wrong. In your engagement it is part of the design.
04 · scope discipline

When the right answer is to not build it

On its own product, Chromatic declined features that would have traded user trust for growth — engagement mechanics, share-gated value, claims the product could not stand behind — at a cost to speed and revenue. Each refusal was recorded and has held.

What it means for youThe hard part of advising on AI is knowing what to decline, and making the refusal stick.

Portfolio

Built on the system.

Chromatic Ventures is the holding company; these are its products and operating businesses. Where a build is public, you can try it.

Prism
FlagshipNative iOSIn development

Prism

A 300-term structured taxonomy on a perceptually uniform colour coordinate system — SwiftUI with Metal shading, on-device analytics built privacy-first, an accessibility standard held at zero violations.

Join the TestFlightAbout Prism
Arise
iPhoneIn build

Arise

An alarm that wakes you in a familiar voice and walks you into a “start my day” sequence instead of a snooze loop.

Join the TestFlight
Interactive HTML course
HTML · downloadFree

The Complete Claude Mastery Course

A standalone interactive HTML file with sidebar navigation, search and progress tracking. Open it in any browser. No account, no tracking.

Download HTML · .zip
Crown Sports Floors
Operating businessCalgarySite in progress

Crown Sports Floors

Hardwood sports flooring. An operating business in the Chromatic group, and the first site being rebuilt on the same system that built this one.

Visit when live

Writing · weekly

How the system is built, and where it breaks.

One piece a week on running a business with agents: operating rules, drift, decision records, and the failure modes nobody warns you about.

  • How to structure agent operating rules

    What each role may read, propose and change — and why “may not” is the more important half.

    Coming first

  • What drift looks like, and how to catch it

    The written rule and the running system will diverge. A pattern for finding where.

    Next

  • Why a decision ledger stops a project eating itself

    Recording what was decided is easy. Recording what it superseded is the part that saves you.

    Then

Get each piece by email. One a week, no more. Subscribe (form to come)

About

Sam Visser, founder.

Product builder based in Calgary. Over the past eighteen months he designed, engineered and shipped a native iOS application without a team — roughly 55,000 lines across 231 files — and, to make that possible, built the operating system Chromatic now delivers to clients. It is organisational design applied to non-human collaborators, and it has been through enough real conditions to be hardened rather than theoretical.

Background in finance (BBA, St. Francis Xavier University).

The long version
Portrait to follow

Before you send a request

The questions that usually come first.

Who else have you done this for?

Two businesses are underway now: website rebuilds with operational agents in scope. Before that, the system ran Chromatic’s own software company for eighteen months — including the parts that failed, which is what you will be shown.

Isn’t this just prompt engineering?

No. Prompts are one line of it. The work is deciding what each agent is allowed to change, how decisions get recorded so they survive, and what catches the system when it is wrong. That is organisational design, not phrasing.

What does it cost?

Engagements are quoted as a fixed scope after a short discovery, not as a day rate. Send the request with enough detail and you will receive either clarifying questions or a proposal outline within two business days.

What if the models change?

The operating rules outlive the model. Roles, permissions, decision records and verification layers are the same whichever system runs underneath. Chromatic has already changed models under its own system without rebuilding it.

Can’t we just buy a tool?

You can buy tools. What you cannot buy is the decision about what your business will and will not let a machine do unsupervised. That answer is specific to you, and it is the part that matters.

How long does it take?

Six to eight weeks to something running. Longer to something you would trust unsupervised — better to say that now than to discover it together in month three.

What do you need from us?

Access to how the work actually happens today — the people, the tools, the documents — and one decision-maker who can ratify what the system is allowed to do.

Request a proposal

Tell us about the work. We’ll tell you whether it fits.

A few minutes of detail here replaces a discovery call. Requests with real substance get a proposal outline, or the questions needed to write one, within two business days.

  • Minimum detail is enforced on purpose. It keeps the queue serious and produces a better proposal.
  • Nothing you write is shared, sold or used to train anything.
  • Calgary, Mountain Time. Replies from Sam, not a sequence.

Prefer email? hello@chromaticventures.ca

Please add your name.
Which business is this for?
A working email, so the reply reaches you.
Include https:// if you add one.
Choose the closest fit.
Be concrete — this is what the proposal is written from.0 / 200 min
At least 200 characters, so the reply can be specific.
Includes “nothing yet”, with the reason.0 / 80 min
At least 80 characters.
Pick the closest.
A range is enough.
Fill in the required fields to send.

Received

Thank you. You will hear back within two business days.

Expect either clarifying questions or a proposal outline. If the fit is not there, you will be told that too, with a pointer to something that might fit better.

Preview: nothing was sent. In production this posts to a Cloudflare Worker, notifies Sam, logs the request, and sends a plain-text acknowledgement.