1 · Permissions and agreement
/pacto/: roles, majorities, limits, and hard limits. Who can read, propose, approve, or carry out is written in each rule. The closed list of verbs is not published.
System
Agents read the rules. Every decision stays in the record.
Clear rules for people and agents.
Each area is a folder and each rule a file. Permissions are the roles. History is the record.
- folder → area
- file → rule
- permissions → roles
- history → record
Architecture
How Yulen works, inside.
A diagram of the parts on this page. Anything drawn with a dashed line is not published.
2 · The /tu-empresa/ tree
Rules in open files (.md): pacto/, cultura/, objetivos/, dinero/, relaciones/. Readable and downloadable.
3 · Versions
History per rule and the reason for the change. The exact history format is not published.
4 · Execution
An action inside the current rules runs. Outside the plan, the person who should decide is asked.
5 · Record /registro/
Read only: who, when, and why. Every decision, permission, and change, with evidence ready to review.
Connections
MCP, API, or browser. The specific integrations, such as bank, payments, customers, ads, support, or AI, are not published.
How Yulen works, inside.
The tree
/tu-empresa/
pacto/
Governance: socios.md, mayorias.md, lineas-rojas.md.
cultura/
How you work: valores.md, atencion-cliente.md.
objetivos/
Strategy: 2026-T4.md, plan-marketing.md.
dinero/
Money: presupuesto.md, gastos.md, cobros.md.
relaciones/
Customers and suppliers: proveedores-aprobados.md.
registro/
Evidence, read only: who, when, why.
/tu-empresa/
/tu-empresa/
Step by step
Three steps. Anything outside the plan gets asked.
- 01 · Write the rules
In: the shareholders' agreement, goals, budget, and what is never done. Whether it comes in as documents or as a conversation is not published.
Out: current rules, with roles, permissions, majorities, and hard limits. A person approves. An agent can propose. It cannot approve.
- 02 · Agents work inside them
In: tools connect by MCP, API, or browser. The specific integrations are not published.
Out: work done inside the rules. Anything outside is asked of the person responsible.
- 03 · Every decision is recorded
In: every action by people and agents.
Out: a record of who, when, and why. If you change provider, the context leaves in an open format.
Three steps. Anything outside the plan gets asked.
Three steps. Anything outside the plan gets asked.
Where it sits
The rules sit between the company and its tools.
People agree, approve, and decide what matters. Agents carry work out inside the rules. Yulen keeps /tu-empresa/, the permissions, the limits, the hard limits, and /registro/.
The rules sit between the company and its tools.
Anatomy of a rule
/tu-empresa/dinero/gastos.md
- 01 · Header
dinero/gastos.md
- 02 · Version
v3 · current · an illustration, with no date
- 03 · Owner
approved by two partners.
- 04 · Conditions
agents carry out a first band. Above that, one partner. Above that band, two partners. Ads: a monthly cap. No amounts: the example publishes no figures.
- 05 · Never
pay suppliers that are not approved.
- 06 · History
from v1 to v3, with a date and a reason on each version. The history format is not published.
/tu-empresa/dinero/gastos.md
One decision
From the proposal to the record.
- 01 · Propose
The marketing agent proposes raising the ads budget. An illustration, with no date.
- 02 · Agree
Two partners review and adjust the figure.
- 03 · Approve
It is approved according to the agreement. gastos.md v4 is born.
- 04 · Follow
Campaigns use the new limit. Anything above it is asked.
- 05 · Record · always
Each run links to v4.
From the proposal to the record.
From the proposal to the record.
Record
This is what the record looks like.
/registro/ · read only · an illustration.
- Example · finance · paid an approved supplier · rule 1
- Example · finance · asked for approval · rule 2
- Example · one partner · approved an exception
- Example · marketing · ad blocked by the budget · rule 4
- Example · two partners · approved dinero/gastos.md
What you receive
The company file.
/tu-empresa/
The company tree: agreement, culture, goals, money, and relationships as rules in open files (.md), readable and downloadable.
/pacto/
Roles and permissions: majorities, permissions, budgets, and hard limits.
/registro/
Every decision, permission, and change, with who approved it.
/capacidades/
Capabilities you can turn on: commercial, product and engineering, finance and operations, customer support.
/conexiones/
Integrations by MCP, API, or browser. The real integrations are not published.
/versiones/
History per rule, with earlier versions and the reason for the change. The format is not published.