Contact
One channel, stated plainly: direct correspondence. No form, no account, nothing collected on the way in, and no promise a reply cannot keep.
On this pageWho you are writing toWhat is worth writing aboutThe channelWhat to include
Who you are writing to
SI — Systems Intelligence is the name used for a body of work on connecting artificial intelligence, automation and infrastructure into systems that work together, with people in control. Correspondence reaches a person who works on that directly — not a queue, a ticket system or an agency.
This page is the only public contact route for the project. If a message arrives from anywhere claiming to represent SI, this site is the reference point for whether that is true.
What is worth writing about
- A specific technical question about something described here — the four-stage model, agentic scope and oversight, integration contracts, observability.
- A correction. If this site states something inaccurate or ambiguous, say which page and what is wrong. Corrections are the most useful messages this address receives.
- Research or writing that engages with the material and wants a source, a clarification or a check on how a term is being used.
- Working on something adjacent where an exchange of notes would be useful.
What this address is not for: sales enquiries, recruitment, link requests, unsolicited proposals or automated outreach. Those are read as noise and are unlikely to get a reply.
The channel
Direct correspondence
Plain email. No form, no account, no confirmation sequence — your message arrives as a message, not as a record in a marketing system.
There is deliberately no contact form on this site. A form would mean a submission endpoint, validation, spam handling and a retention question: three new ways for data to exist, and one more thing that has to keep working. An address does the same job with none of that.
What to include
A message is easiest to answer when it contains:
- The subject in the first sentence, rather than a preamble.
- The context that matters — what system, what constraint, what you have already tried.
- What a useful answer would look like — a direction, a reference, a decision.
- How much detail you want back — a sentence or a page.
Privacy-conscious communication
Please send the least personal data that answers the question. Do not send credentials, API keys, tokens or recovery codes — nothing here asks for them, and they should not travel by email either. Avoid pasting production configuration, customer records or anything confidential; describe the shape of the problem instead of the data inside it. If a conversation needs sensitive material later, ask first and a better channel can be agreed.
Nothing you send is added to a mailing list, and this site stores nothing about the visit that brought you here — see Privacy.
What a reply does and does not commit to
Correspondence is read by a person. It is not a support contract, a service agreement, a quote, a proposal or an acceptance of work, and no response time is promised. Anything discussed stays a conversation until it is written down as something else, deliberately and in writing.
No products, services, prices or commercial offerings are published on this site, and writing to this address does not create an engagement.
For what SI is and what this site does not claim, see About. For answers that need no conversation at all, the questions page and llms.txt cover most of it.