
The End of Software Engineering and the Rise of Agentic Engineering
One account of agent systems explains why decision logic migrates from source code into a model that writes code at run time. Another proposes a...
The End of Software Engineering and the Rise of Agentic Engineering
Under stated assumptions there is a structure-preserving interpretation of the four pillars of agent externalization, memory, skills, protocols and harness, in the ArchAgents Architecture triple (G, Know, Phi); three production systems, ContextFS, AgentHero and CatDB, realise it on identifiable fragments, and the series states where it fails.
Each part fixes one pillar against one production system at a pinned commit, and states which conditions hold, which hold on a restricted fragment, and which fail.

One account of agent systems explains why decision logic migrates from source code into a model that writes code at run time. Another proposes a...

Agent memory is often called coalgebraic state, and the description rarely goes past the letters. We fix a functor, a set of laws, and a way of...

The claim that skills are operations of a coloured operad is testable only after its colours, operations, substitution, and semantics are specified....

The categorical reading of agent architecture assigns the protocol layer to the syntactic wiring G of an architecture triple (G,Know,Phi). We make it...

An agent harness surrounds a language model with tools, memory, wiring and policy. Banu proposes that this layer is already described by the...
The four parts are read in order: each layer’s interpretation is stated using the definitions the previous layer exports, and each adds one property while carrying forward the failure modes already found.
Lineage runs on a single time axis, so ancestry is fixed once recorded and later derivations cannot rewrite it.
Composition is substitution-closed on a restricted colour set, well founded whenever sibling output keys stay disjoint.
Every port is typed, and every way of declining is a distinct, observable outcome rather than a silent failure.
Certificates carry a scope and a decidable replay check, so what a run claims can be checked against a receipt.
Every claim is checked against one production system at a pinned commit, not against a reference implementation built to satisfy the theory.
a93035d1c3ad247cc9341aBrowse the code-evidence layer for the file and line references behind every checked claim.