M / manifesto
manifesto

Autonomous engineering needs autonomous security.

MatterSec exists because software work is changing from human-only authorship to agent-executed labor. That new labor needs a security supervisor that can act.

The agent ran without a witness. Matt is the replay.

§ 01

Agents are becoming software engineers.

They do not just autocomplete code. They take tasks, modify repos, run commands, open PRs, and work while humans are elsewhere.

§ 02

Security cannot remain a post-merge ritual.

Autonomous code needs security controls inside the loop, where risky changes are created and can still be stopped.

§ 03

The reward must be earned safely.

As coding agents optimize for tests, tickets, and PR acceptance, teams need a way to verify the success signal was not gamed.

§ 04

Humans should supervise the system, not every edit.

MatterSec gives humans a control room. Matt handles the repetitive enforcement path and explains the exceptions.

§ 05

Every autonomous run should be replayable.

If an agent changes code that matters, the team should know what happened, why it happened, and what action was taken.

Subho Halder · MatterSec Labs · 2026