01 · PositioningTechnology holding · Peru
DARXI doesn't sell hours or deliver one-off projects. It runs its own agent orchestrator —routing, memory, evaluation, and safety control— and every product in the portfolio comes out of it. What accumulates isn't a catalog of jobs: it's the machine that builds them.
Eleven products across eleven different sectors —international logistics, business intelligence, clinical nutrition, live commerce, academic research, live gaming— don't come from a large team. They come from a machine that splits work across agents, picks the right model for each task, evaluates the result, and learns from every run.
That's why the defensible asset isn't any single product. It's the ability to open the next one without rebuilding the ground floor — and to do it in a new sector without starting from zero.
Every product is the proof. The orchestrator is the thesis.
Six layers: who can work, how it's assigned, how it runs, what it knows, how it's checked, and where it's operated from. The indigo band marks the splice — below it, the products begin.
178 TypeScript files · 63 tests · 42 phase documents · Local SQLite · MCP — verified 2026-07-28
The figures come from each repository's history: commit date range, commit count, modules, and source files. There are no business metrics in this table because none can be verified today.
Virtual US mailboxes, pre-alerts, package consolidation, and warehouses in Miami and Peru. Seven modules —locker, consolidation, warehouse, B2B, storefront, travelers, and admin— on its own containerized infrastructure.
BI platform over billing data: locked incremental sync, customer and sales catalog, role-based dashboards, and Power BI output. The repository with the longest history in the group.
Operating system for clinical nutrition: energy expenditure and macronutrients over Peru's official food-composition tables and PRISMA household measures. The product's rule is that every result must be auditable — never a black box.
Live-selling platform for boutiques that today run by hand across a stream, comments, and a spreadsheet: real-time stock holds, order close-out, and an admin panel in a single flow.
Autonomous Thesis Intelligence System. Core, domain, SDK, CLI, plugin registry, schemas, and templates to produce and review a complete thesis with editorial traceability. Version 1.0.0 declared stable.
Interactive RPG for TikTok Live: the audience plays from the chat, with combat, music trivia, and a betting economy. Backend, frontend, and an overlay layer on the stream, plus the platform connector.
Documentation and research center on labor rights in Peru. Documents to a forensic standard and backs the defense through the last instance. It's the only piece of the group that isn't for profit, and the first with its own domain live.
Group buying: presale campaigns, prices that drop as units accumulate, catalog, and inquiries. Its monorepo proved the vertical-package pattern — the business logic lives apart from the core.
Legal AI product built under a zero-hallucination constraint: every answer has to trace back to a verifiable source.
Course platform with instructors, enrollments, and profiles on Postgres with row-level security. The full schema lives version-controlled as SQL in the repository.
Native app with home-screen widgets. It's the only piece of the portfolio off the web: when the domain calls for native, native gets built.
They're fixed in the holding's executive system and are the mold every new product inherits. None of them rests on convention: import boundaries are checked by dependency-cruiser, and environment-variable access, by a rule from eslint.
Engineering constitution, founder operating system, architecture decisions, and work packages. It's the body of work that turns ‘we know how to build’ into ‘we know how to build it the same way again.’
| Body | What it fixes | Pieces |
|---|---|---|
| Engineering constitution | Architecture principles, standards, quality gates, RFCs, and ADRs | 13 |
| Holding operating system | Task, document, evidence, risk, and calendar registries | 32 |
| Architecture decisions | Repository location, data engine, hosting, authentication | 7 |
| Work packages | Build units with closed scope | 4 |
| Full collection | Everything above plus execution, synthesis, and audits | 525 |
All the geometry lives as code in a single source file, and every asset is generated from it. Nothing is auto-traced: every node is placed by hand on a grid with a cap height of 100.
For a studio that claims to do architecture, publishing the system isn't vanity — it's the product in plain sight.
View the brand guide (Spanish)The orchestrator can open a product in a new sector in weeks. What it can't manufacture is the judgment of someone who's spent years inside that sector, or their client book. That's where a partner comes in.
We're not raising a round. For each vertical, we're looking for the person who knows why the obvious version of the product is wrong.
The engineering is solved; what's scarce is domain judgment. An operating partner tells you what's urgent for a real customer and what's a nice-looking feature nobody will use.
A product with no channel is a demo. We're looking for partners with access to their sector's buyer —clinics, boutiques, studios, importers— more than with capital.
The asset is the orchestrator, not any single product. A capital partner who doesn't share that reading will end up asking for the opposite of what grows the group.
Open sectors
Tell us your sector and what you bring — capital, channel, or domain judgment.
[email protected]The group's rule forbids padding with filler. This data isn't in any repository, so it's missing in plain sight instead of showing up invented.