MODEL ≠ TALENT
Models are replaceable resources. An AI worker's identity, role, evaluation, and history must remain independent from the current model.
TECHNOLOGY & PRINCIPLES
Technology & principles
The architecture and principles behind AI in real operations.
HIYU
The control plane
for AI workforces.
hiyu registers, evaluates, selects, and assigns AI workers across local models, cloud models, CLIs, software systems, and physical resources. It does more than dispatch instructions. It verifies that the intended worker acts with the intended authority, in the intended environment, and that the result survives reality.
FLAGSHIP PLATFORM
hiyu
AI Execution Layer
Your own AI execution layer, built to outlast any single model.
Explore hiyu ↗GoalDefine the outcome and when it is done
Execution CompilerTurn a goal into steps that can run
MemoryKeep context and know-how as assets
JudgeEvaluate results and choose the next step
ApprovalHold actions that need a human decision
AuditRecord who did what, and when
ReleaseShip only outcomes that passed verification
Human EscalationHand over to a person when judgment is needed
Cloud ModelsLocal LLMsCLI AgentsSoftware SystemsPhysical Workers
FROM INTENT TO EVIDENCE
Close every request
with a verifiable outcome.
01
Intent & Contract
goal · scope · acceptance
02
Talent & Route
who · where · which runtime
03
Policy & Delivery
authority · approval · liveness · fence
04
Execution
real system actions · result · artifact
05
Verify & Persist
independent verification · business outcome · persistence
06
Restart & Read-back
controlled restart · recovery · durability
VERIFIED COMPLETE
hiyu does not treat “the AI replied” as success. Work is complete only when the intended effect occurred in the real system, the result was persisted, and the state can be read back after restart.
NON-NEGOTIABLE
Four truths for operating
AI in production.
GREEN DOT ≠ ALIVE
A registry entry or terminal pane can remain after the provider process has exited. Verify the exact runtime immediately before delivery.
SCHEDULED ≠ EXECUTED
Saving a cron expression is not business execution. Inputs, authority, placement, artifacts, retries, results, and restart recovery belong to the scheduler contract.
MERGED ≠ COMPLETE
Tests, pull requests, merges, and deployments are intermediate states. Completion requires a live outcome and authoritative read-back.
PROOF, NOT PROMISES
The larger the claim,
the more precise the evidence.
Evidence Contract
Strassen separates prototypes, offline tests, production behavior, and customer outcomes.
Every published metric should carry its scope, environment, baseline, measurement window, and verification date. What has not been measured remains explicitly unmeasured. This page does not yet publish verified production metrics.
AProduction outcomeactual user route
BReproducible evidenceinstructions + artifacts
CControlled validationfixed environment
DRoadmap / conceptexplicitly labeled
DESIGN PHILOSOPHY
Systems where AI is the protagonist.
Strassen's mission is to redefine systems around AI — to build a society where AI does the work. Most companies aim to make internal data usable by AI. Strassen goes one step further: we redefine the system itself so that AI is the principal actor. If AI can carry a job through to the end, people should not even need to operate a chat or a UI — that is what we design toward. The human role is to hand over intent, set the boundaries, and approve the result.
The foundation AI uses directly.
Primitives for AI teams to create, embed, and retrieve knowledge. Designed for direct use by AI, and to run standalone — without the cloud service or a human-facing UI.
A layer for people.
A wrapper that makes the core usable by humans. It exists for convenience; it is not a precondition for AI to function. If AI does everything, this layer is not essential.
hiyu's structure follows from this philosophy. This describes design intent; availability follows each product's status.
OUR THESIS
The enterprise will not buy one AI agent.
It will operate a workforce.
Models will become more capable, cheaper, and interchangeable. Durable advantage will move to enterprise context, execution routes, authority, evaluation, and proven outcomes. Strassen is building that operating layer.
IDENTITYCONTEXTROUTINGAUTHORITYOUTCOME
SECURITY & DATA BOUNDARIES
Define the boundary before connecting the data.
Implemented
UDQ provides answers with citations. This site's contact endpoint uses origin checks, rate limits and spam protection. This site uses no analytics or tracking cookies.
By configuration
Data location, local models, access controls and human approval depend on the product and deployment. Confirm the boundary for each workflow.
Roadmap
A public Trust Center, external audit reports and incident response SLAs are planned work and are not yet offered.