How we build

Agents draft. A person ships. Git is the source of deploy.

The same constraint applies to client work and to this site. Anything hard to undo waits for a person. Delivery is defined in the repository. Secrets stay out of it.

Agents and human review

Specialists draft, classify, and research. A coordinator puts that work on a queue. A person approves mail, posts, spend, and other actions a client would see.

The gate is there because those actions are hard to undo. A wrong draft can be rewritten. A wrong send cannot. The Dream Team page describes the roles and publishes four vendor-neutral Reference Agent Blueprints (.yaml). The review path is the same picture.

How we talk about scope and client data is on Approach.

Text version: specialist agents do bounded work, a coordinator places it on a review queue, a person approves, and only then does an external action go out.

Defined in git

For this site, every change is checked and built, then a person reviews it before the public site updates. A step that is not written down gets skipped, and nobody can see that it was skipped.

Self-hosted pilots and agent lane boundaries are defined in git for the same reason. Inspect the portable YAML manifests under Reference Agent Blueprints for how read scopes, hard write boundaries, and verification artifacts are declared in version control.

Continuous integration

Text version: a change lands in git, a type check and the production build run, a person reviews, and only then does the public site update.

  • Every pull request runs a type check and the production build.
  • A person reviews the change before the public site updates.
  • Merge to main is what updates https://ai.skeen.biz.

The check runs. Whether the repository requires it before merge is a setting, and this page does not claim that setting is on.

Security principles

  • A person approves anything external. The failure mode is an action that cannot be unsent.
  • No single agent holds untrusted input, privileged credentials, and an external send in the same turn. Those three stay in separate lanes.
  • Per-origin service tokens isolate each application. A 90-day expiry alert fires before a token lapses. Tokens are not shared, and they are not pasted into prompt context. A local loopback bridge holds the credential at the edge. The inventory of connected systems is not listed here.
  • Monitoring lanes are read-only GET. Writes and sends wait on the human gate.
  • Discovery runs only after a cryptographically signed scope authorization file is verified.
  • Private documents stay on systems we operate. Copying the corpus to a public model is a leak, not a draft.
  • Offsite backups are encrypted (.age). Recovery is marked green only after an automated ephemeral Postgres restore checks table and row counts.
  • Where a page must not phone home, the policy sets connect-src to 'none', and a check fails if a request leaves the origin.
  • Secrets stay out of code. A secret in git is a secret in history.
  • This site is reviewed before it is public.
  • Reviews that matter are written down, so the next person can see why a gate was there.

What stays manual

Publishing this site. Sending on behalf of the practice. Spending money. Steps where a mistake is hard to undo. Automation stops at the draft or the queue.

Schedule a conversation