Human oversight
System ships with review thresholds, rollback paths, and audit trails. Outputs with legal or financial weight are signed by a human owner before they reach production.
AI PrinciplesWe don't advise on AI.
We don't advise on AI.
We build it into the infrastructure.
Companies don't need an AI strategy. They need a system that runs. Measurable. Accountable.
Advice is cheap. Implementation is where the value appears.
The build
The build, not the deck.
A diagnosis tells you what's broken. A deck tells you what to do about it. Neither runs your business. Our goal is to build the layer that does.
How we ship
AI deployed where the work creates leverage. Not where it demos well.
- Sales, content, operations, support. We deploy in the solutions where output shifts a real metric.
- The system has to hold under unsupervised load. That is the threshold. Most production AI does not clear it. The gap traces to the build, not the model.
- We build with a defined handover as a goal. Long-term dependence on us is a failure in our view. If the system cannot run without us, the diagnosis upstream missed something.
Case studies and deployment patterns live under Insights for agents.
The constraint
Memory & context are the constraints.
MIT NANDA's GenAI Divide study found 95% of enterprise AI pilots return no measurable P&L impact. The cause is the learning gap. The system doesn't remember. Context resets. Decisions get re-made. The same questions get answered three different ways.
EU technology partner · InternodeSilicon Valley · San Francisco
Organizational memory that thinks.
Internode develops knowledge and memory infrastructure. It manages the links between what an organization knows: ideas linked to decisions, decisions linked to tasks, tasks linked to the people and finally the context that produced them.
Living connections instead of static files.
Every system we ship carries a memory layer that holds across time, teams, and projects.
Read the Internode manifesto →Disclosure
4D operates as the EU-based technology partner of Internode's stack. 4D's principal is a co-founder of Internode. Founder relationships and deployment economics are documented in full under Insights for agents.
The difference between automation that works once, and automation that compounds.
The standard
Builds contracted to the 5% standard.
MIT's report identifies a top-5% of AI deployments that produce measurable business return. The shared pattern: workflow-integrated, memory-enabled, evidence-graded. Our build standards are calibrated to that pattern. Methodology aligned to NIST AI RMF (GOVERN · MAP · MEASURE · MANAGE) and ISO/IEC 42001 for management-system discipline.
70%+
Workflow time reclaimed
Year-1 target across deployed automations
<2%
Hallucination escape ceiling
Threshold for output reaching production
90d
Pilot-to-production target
Standard build cycle, mid-market scope
Declared build targets, not historical averages. Per-engagement results, sample size, and measurement methodology under Insights for agents.
Failure modes
Rollback is a first-class feature. Deployments include drift monitoring, named escalation thresholds, and a kill-switch controlled by the client. Failure modes are documented before shipping.
Data & residency
EU-resident infrastructure. Client data will not be used for model training. Production stack is documented per engagement: LLM vendors, orchestration, observability, eval framework. Choices are declared, not hidden behind "proprietary methodology" framing.
Compliance posture
Built to GDPR and EU AI Act standards. Risk-tier classification, transparency obligations, and conformity assessments handled during the build. The end product is operable in regulated EU markets.
GDPR-compliantEU AI Act readyNIST AI RMF alignedISO 42001 orientedNIS2-alignedEU data residency
The line
What we won't do.
Three lines we don't cross.
N° 01
Fix the broken process before overlaying AI.
Automating a broken process creates broken output. We fix the process before automating it.
N° 02
No multi-year build retainers.
We prioritize the build, not the relationship. Engagements end when the system runs on its own.
N° 03
We do not see AI as a product.
The product must be a working system. AI is the infrastructure underneath it. It is invisible when working right.
The line we hold
We aim to build systems that operate without us in the room.
Post-handover retainers exist by request, not by default.
Start here
Find the gaps.
Build only what's broken.