Security and authority

Models reason.Owners authorize.Authorities act.

Understanding a request never gives a model permission to carry it out. In BIRTH, every action crosses a boundary that belongs to you.

01The boundary

Every action takes the same route.

Reasoning and action are separated by design. Between them sits the one step a model cannot perform: your authorization.

ModelProposesInterprets the request and drafts a plan.
OwnerAuthorizesApproves, narrows or refuses the plan.
AuthorityActsPerforms only what was approved.
BIRTHObservesReads what actually happened.
BIRTHVerifiesChecks the result against the plan.

02Permission

Permission you can read, narrow and take back.

Once

Approve a single action. Nothing carries over to the next one.

For a scope

Allow a kind of action, in one place, for as long as you choose.

Routine

Let reads and low-risk upkeep run inside limits you have already set.

Never

Rule something out entirely. BIRTH will not ask again.

Some steps always wait for you, whatever you have allowed before: sending something in your name, spending money, deleting work, changing a live system, or granting a new permission.

03Privacy

Your computer is not a data source.

BIRTH is designed around keeping your information where you keep it, and making every exception visible.

Local processing

  • Work that can happen on your computer happens there
  • Your files and knowledge are not collected to build a profile
  • What BIRTH remembers is yours to inspect and remove

Connected services

  • Reached only for tasks that need them, and only if you allow it
  • Each connection is listed in Settings, with what it can access
  • Revoking one takes effect everywhere at once

04Receipts

Everything BIRTH does leaves a receipt.

What was asked, what was approved, what was done and how it was checked — kept together, in words you can read.

  • Who authorized the action, and for what scope
  • Which authority carried it out
  • What BIRTH observed afterwards
  • Whether the result matched the plan
ReceiptIllustration
Request
Reply to Ana with the revised timeline
Reasoned
Draft prepared from the thread and the project plan
Authorized
By the owner · this message only
Acted
Mail authority · 1 message sent
Observed
Delivered · attachment included
Verified
Matches the approved draft ✓
An illustration of the receipt concept — not a product capture.

About this website

This page describes how the BIRTH product is designed. How birth-systems.com itself handles enquiries, uploads and data is set out separately in the website privacy and security notice.