Criterio EA

Executive office

Evidence before the decision

The executive’s office, prepared for every meeting

Name: Criterio EA (Ofelia)
Author: José Ñáñez

Ofelia sets the executive’s week beside the meetings and commitments: what clashes, which meeting has no materials, which minutes are still unsigned, which agreement has no owner or date and which email is waiting for a reply. She prepares each decision with its options and evidence, without ranking them. She does not send, schedule or decide.

What it costs, measured by third parties

57%

of working time goes to communicating —meetings, email and chat— and 43% to creating

57 of every 100 hours

Microsoft, Work Trend Index 2023, «Will AI Fix Work?», 2023 · Sample: Aggregated Microsoft 365 usage data, not the survey; the report does not give the size of that sample ↗

55%

say the next steps at the end of a meeting are unclear

55 of every 100 people

Microsoft, Work Trend Index 2023, «Will AI Fix Work?», 2023 · Sample: 31,000 full-time employed or self-employed workers in 31 markets ↗

68%

do not have enough uninterrupted focus time in their workday

68 of every 100 people

Microsoft, Work Trend Index 2023, «Will AI Fix Work?», 2023 · Sample: 31,000 full-time employed or self-employed workers in 31 markets ↗

Third-party figures, each with its source, year and sample, verified against the publisher’s own text. The agent’s own figures are further down, in the test evidence.

Install Support the work Repository ↗

Criterio is open source. If it creates value for you, help fund testing, documentation and the next capabilities.

Ofelia is Criterio’s EA family, an open platform of agent families. See the families

Offices

Where Ofelia is tested, and why she needs no country map

Ofelia processes nothing specific to a country: no invoices or regulations, only the calendar, the minutes and the email. That is why her test is counted in offices, not countries: two with defects seeded on purpose and two controls, where any signal is a failure. What does change from one office to another is how its calendar and email provider exports.

A bank’s president’s office
Colombia
32 documents · 10 defects seeded on purpose
Round 1
10 of 10 signals, none extra
17 of 17 data points
Verification after the fix
50 of 50 signals, none extra
51 of 51 data points
What failed, with its defect: EA-9
A credit union’s general manager’s office
Ecuador
42 documents · 6 defects seeded on purpose
Round 1
4 of 4 signals, none extra
16 of 17 data points
Verification after the fix
35 of 35 signals, none extra
45 of 45 data points
What failed, with its defect: EA-6, EA-9
Control office
Colombia
23 documents · no defect: any signal would be a failure
Round 1
no signal expected · 1 extra
21 of 22 data points
Verification after the fix
no signal expected
22 of 22 data points
What failed, with its defect: EA-7, EA-8
Control office
Ecuador
23 documents · no defect: any signal would be a failure
Round 1
no signal expected
22 of 22 data points

What the material also tests

A meeting in another time zone that only clashes after the clock change
A free event and a cancelled one that clash with nothing
An old calendar: it warns and computes no clashes
A draft put in the minutes folder, which does not count as minutes
An excluded folder, which is neither processed nor mentioned

Criterio · EA family

One agent for the executive's office

She prepares the calendar, each meeting with its decisions, the draft minutes and what needs a reply. She does not decide or send anything.

CRITERIO · EAREADY

OFELIA

The executive office

ROSTRUM

The portal

THE OFFICE RECORDSEach item with its citation. A decision's options go as the documents bring them, unranked.

PRINTER · CRITERIOSHEET 1

CRITERIO · EA FAMILY

Where the family stands: built and tested. The engine passes its deterministic test against four synthetic offices —two with seeded defects and two controls— and the agent passed the full round with a key she never sees. Next are travel and the exports of each provider.

Where each name comes from

Ofelia: · from the Greek ōphéleia, «help»: she is the one who prepares
Rostrum: · from the Latin rostrum, the speakers’ platform of the Roman forum: it holds up what is already written, where others can read it

Ofelia and the portal

What she does, what she never does and what her work looks like

Ofelia installs on her own, and Rostrum publishes her report only if the office decides so. The screenshot is Rostrum on the test office of a financial entity’s president, as the round with the agent left it.

criterio-assistant

From the Greek ōphéleia, “help”: she is the one who prepares.

Processes the exported calendar, each governing body’s meetings and the saved correspondence: the week against the meetings and commitments, each meeting’s pack with the record of each decision, the draft minutes and what is waiting for a reply. You send and decide.

What only she does

Checks every agreement in every set of minutes against its owner and date, and counts how many times each commitment moved. Prepares each decision with the options the documents bring and their evidence, without ranking them.

What she answers

Which of the executive’s meetings clash, also after a clock change
Which meeting is missing its materials by the configured number of days
Which meeting still has no signed minutes
Which agreement in the minutes has no owner or date
Which commitment fell due without a document to back it, or moved more times than configured
Which pending decision has its deadline close
Which email asks for a reply past its deadline

Never

Sends, schedules, accepts or moves anything; recommends an option, prioritises for the executive or evaluates a person.

The president’s office as of 26 October with 10 open signals: an overdue commitment with no document to back it, a supervisor’s request with no reply and two calendar clashes, one only after the clock change.Screenshot of Rostrum on the president’s test office, cut on 26 October 2026. It is test material written by the repository; it belongs to no organisation.

Extends: Whoever assists the executive
Instances: One per executive
Setup: 15 min · 6 questions
Cadence: Every day it runs, with one summary a week; if nothing is due, it stays quiet
Needs from you: The calendar exported and the emails that matter saved in her folder

Set up with/criterio-assistant:ea-setup

Its commands, by group

Start and rhythm2 commands+

ea-setupea-wake

Process1 command+

ea-scan

The week and the meetings3 commands+

ea-agendaea-prepea-minutes

Commitments and mail3 commands+

ea-commitmentsea-mailea-weekly

9 commands · 6 skills

In Rostrum

Ofelia’s report is not published in Rostrum by default: the executive’s office is among the most sensitive things an organisation has. If the configuration says so, it goes in like any other family, and Rostrum shows what her engine already wrote, with the date it wrote it.

How it enters the portal

Ofelia runs /criterio-assistant:ea-setup, leaves its configuration in .criterio/direccion/<executive>/ and marks its root folder with _CRITERIO_DIRECCION.txt.

If its configuration says it is published, Rostrum adds it to the map and raises the portal; if not, server-setup names it among those not published:

/plugin install criterio-server@criterio
/criterio-server:server-setup
/criterio-server:server-start

What it has in Rostrum

Home: The Criterio EA card, with Ofelia and her open signals.
The family: Her engine’s latest output, its signals in words and its reports as the engine left them.
What falls due: The meeting without materials, the pending minutes, the commitment falling due and a decision’s deadline, alongside the other families’.
Where she works: The full path of the office folder with its mark, of the state and of the configuration.
Ask: A written question for Ofelia, which she answers on her next run.

The Criterio EA page in Rostrum, on the test office of a financial entity’s president, published on purpose for the screenshot.

Rostrum: install, configure and use it with every family →

What it costs you today

The work Ofelia prepares, priced with your own numbers

Ofelia extends whoever assists the executive. Enter how many people assist them, what they cost and how many hours a week each task takes them. Nothing you type leaves your browser.

I work in

Write the costs in the currency you choose. There is no conversion: changing the currency clears the costs, because an exchange rate written into a page is wrong within weeks.

The people

Whoever assists the executive

Loaded monthly cost per personFully loaded: salary, benefits and overhead.

USD

Hours per week on each task

Checking the week’s calendar against the meetings and commitments/ea-agenda

Building each meeting’s pack: the agenda, the materials and the record of each decision/ea-prep

Drafting the minutes from the notes/ea-minutes

Following each set of minutes’ commitments with their owner and date/ea-commitments

Sorting the correspondence that needs a reply and preparing the drafts/ea-mail

Hours are per person, per week. The starting people and hours are examples: replace them with yours. The cost is yours to write: we do not print one we cannot source.

Your numbers · per year

Ofelia

Whoever assists the executive · 14 h a week each (35% of the week)

644 ha year

—a year

Annual cost of the work Ofelia prepares—

Hours a year644 h

Annual cost of the people included—

Share of that cost—

Write the monthly cost of each group to see what it costs.

Rostrum, the server, adds no hours here. Her report is not published in Rostrum unless the office decides so. If it is, Rostrum puts it where the leadership team sees it, and its effect is fewer “what came out of the committee?” emails; we do not measure that yet.

What this number is and what it is not

It is the cost of the hours the office spends today on tasks Ofelia prepares: checking the calendar, building the meeting pack, drafting the minutes, chasing commitments, sorting the correspondence. It is not a saving. The person still reviews, decides and sends.

How many of those hours come back we will publish in the evidence section, with each round’s tests. Until that figure is measured, we do not put it here.

Test evidence · updated with every round

This is what is already measured, with what sample and what margin.

Every figure comes from a real run of the repository, with its count and its 95% confidence margin. The engine is tested on every change to the repository; the agent, in rounds on one office’s material.

How it is tested

2 offices and 2 controls

The engine, on all of them. The agent, so far on all 4 offices of the material, in 2 countries. The control offices carry no defects at all: any signal is a failure.

2 commands per office

Ofelia runs her setup and processing —the commands that process the documents and write the records—, with a token cap set before starting. The rest calculate on those records with the engine, which is tested on every change to the repository.

120 documents

What the material of the measured offices holds, in text, eml, msg, CSV and ics. The key is not counted: the agent does not have it.

9.9 million tokens

The work of the language model (LLM) in round 2, with its verifications. No command was repeated.

A key she never sees

What is expected is written in each office’s key before the run: every seeded signal and every data point the written documents carry.

95% margin

Every figure comes with its confidence margin: it says how much the sample supports, which a percentage alone does not.

Ofelia processes the office’s documentation

Round 2 · 4 offices

What she wrote is graded against the key she never saw: every signal by its name and its key, and every data point in the records against what the written documents carry. Each office counts with its latest run, whatever round it came from; if a defect was fixed, the one that verified it. The first runs, with what they missed, are in the chart and in the detail.

Record data

97.4% or higher

Measured: 100%. The headline is the floor of the 95% confidence margin: what the test supports.

146 of 146 data points extracted from the written documents match the key.

Measured

Verification of EA-9: Ofelia on a bank’s president’s office · Colombia, 51 of 51 data points.

Verification of : Ofelia on a credit union’s general manager’s office · Ecuador, 45 of 45 data points.

95% confidence margin (Wilson): 97.4–100%

Signals found

95.6% or higher

Measured: 100%. The headline is the floor of the 95% confidence margin: what the test supports.

85 of 85 signals the key expected.

Measured

95% confidence margin (Wilson): 95.6–100%

Correct signals

95.6% or higher

Measured: 100%. The headline is the floor of the 95% confidence margin: what the test supports.

85 of 85 signals raised were correct.

Measured

95% confidence margin (Wilson): 95.6–100%

Controls without false alarms

2 of 2

2 of 2 control offices without a single extra signal.

Measured

8 commands run on 4 offices, each with its output, its cost and its grade published.

How the family moves from one round to the next

Each dot is one office in its first run of the round; the line is its 95% confidence margin. Verifications are shown apart: they repeat what was fixed. The axis starts at the lowest value published.

a bank’s president’s office · Colombiaa credit union’s general manager’s office · Ecuadorcontrol office · Colombiacontrol office · Ecuador

Round 1¹

Round 1 · verification²

Round 2³

Round 2 · verification⁴

1 · Round 1: Ofelia on a bank’s president’s office · Colombia, control office · Colombia, control office · Ecuador and a credit union’s general manager’s office · Ecuador.
2 · Verification in round 1: Ofelia on control office · Colombia, after fixing EA-7. Verification in round 1: Ofelia on control office · Colombia, after fixing EA-8. Verification in round 1: Ofelia on a credit union’s general manager’s office · Ecuador, after fixing EA-6.
3 · Round 2: Ofelia on a bank’s president’s office · Colombia, control office · Colombia, control office · Ecuador and a credit union’s general manager’s office · Ecuador.
4 · Verification in round 2: Ofelia on a bank’s president’s office · Colombia, after fixing EA-9. Verification in round 2: Ofelia on a credit union’s general manager’s office · Ecuador, after fixing .

Results by country · each country’s latest run

Each country with its offices in their latest run with the agent. The margin is the 95% Wilson interval.

Country	Entities	Round	Record data	Signals found	Correct signals	Controls without false alarms
Colombia	2	2	76 of 76 · 100%95% CI 95.1–100%	50 of 50 · 100%95% CI 92.8–100%	50 of 50 · 100%95% CI 92.8–100%	1 of 1
Ecuador	2	2	70 of 70 · 100%95% CI 94.7–100%	35 of 35 · 100%95% CI 90.1–100%	35 of 35 · 100%95% CI 90.1–100%	1 of 1

Defects the rounds found · 9

Every error is logged with its origin and the commit that fixes it. It counts as verified only when a run after the fix gives the expected result.

9 Fixed and verified
0 Fixed, to verify
0 Open

Where they came from

the agent’s instructions4
the code2
the answer key1
the test harness1
the test data1

The full statistical analysis: margins, evolution, offices and each failure with its origin →Every output, its cost and its grade, on GitHub ↗

For auditing

The full detail of every run. Each block opens on its own.

Every run in the round13 runs

Ofelia ran her commands on each office’s material, with a token cap set before starting. What she wrote was graded against the key she never saw: every signal by its name, and every data point in the records against what the minutes and the emails carry.

Test material	Agent · commands	Signals	Record data	Tokens
a bank’s president’s officeRound 1 · Colombia	Ofelia · 2	10 / 10	17 / 17	1.4 M + 1.2 M repeated
control officeRound 1 · Colombia	Ofelia · 2	0 / 0 · +1	21 / 22	1.3 M
control officeRound 1 · Colombia · verification	Ofelia · 2	0 / 0	21 / 22	1.5 M
control officeRound 1 · Colombia · verification	Ofelia · 2	0 / 0	22 / 22	2.1 M
control officeRound 1 · Ecuador	Ofelia · 2	0 / 0	22 / 22	1.5 M
a credit union’s general manager’s officeRound 1 · Ecuador	Ofelia · 2	4 / 4	16 / 17	1.7 M
a credit union’s general manager’s officeRound 1 · Ecuador · verification	Ofelia · 2	4 / 4	17 / 17	1.8 M
a bank’s president’s officeRound 2 · Colombia	Ofelia · 2	50 / 50	50 / 51	1.6 M
a bank’s president’s officeRound 2 · Colombia · verification	Ofelia · 2	50 / 50	51 / 51	1.6 M
control officeRound 2 · Colombia	Ofelia · 2	0 / 0	25 / 25	1.9 M
control officeRound 2 · Ecuador	Ofelia · 2	0 / 0	25 / 25	1.2 M
a credit union’s general manager’s officeRound 2 · Ecuador	Ofelia · 2	35 / 35	44 / 45	1.6 M
a credit union’s general manager’s officeRound 2 · Ecuador · verification	Ofelia · 2	35 / 35	45 / 45	1.9 M

The defects, one by one9 defects

EA-1Fixed and verified
Setup stopped: the engine required the entity's tax ID, and no document in the office carries it. Ofelia did not invent it and left the configuration unvalidated.
The office is identified by its executive: the engine no longer asks for the tax ID and the report header does not show it when missing. Both commands were repeated on banking: 10 of 10 signals and 17 of 17 data points.
the code · a bank’s president’s office · Colombia · d11470ea
EA-2Fixed and verified
The inventory flagged the .ics calendar as an «unsupported format», although Ofelia's engine processes it.
The inventory treats as readable the formats the family's structure declares as its own by extension. Verified in the banking repeat.
the code · a bank’s president’s office · Colombia · d11470ea
EA-3Fixed and verified
The citations of the agreements and commitments named the section, not the line: «Commitments, first item».
The skills say each citation points to a line —`line N` or `item N`— and that quoted text goes with it, not instead. Verified in the banking repeat.
the agent’s instructions · a bank’s president’s office · Colombia · d11470ea
EA-4Fixed and verified
The key contradicted two skills: it cited the decision in the minutes that defer it, while decision-brief cites it where the material writes it, and it took a request for a meeting with the executive as routine, while correspondence-record only takes an already approved appointment as routine.
The key now follows the skills. Ofelia had done both right.
the answer key · a bank’s president’s office · Colombia · d11470ea
EA-5Fixed and verified
The harness did not recognise as the same citation one that names the section before the item —«Agreements, item 1»— or one that quotes the line's text in « ».
`tests/ronda_familia.py` resolves the line by «line N», by «item N» even after the section, or by the quoted text, and also applies it to the deadline's citation.
the test harness · a bank’s president’s office · Colombia · d11470ea
EA-6Fixed and verified
The citations of the agreements carried the office folder in front —`direccion/gerencia-general/organos/…`—, so they did not open from the office.
The skill says each citation is relative to the office folder, and the engine reports a citation that is not there as a record issue, to be corrected before calculating. Ofelia was rerun on the credit union: 17 of 17 data points.
the agent’s instructions · a credit union’s general manager’s office · Ecuador · d11470ea
EA-7Fixed and verified
In the Colombian control, Ofelia left open a commitment whose completion was in the meeting's material, and the engine raised an overdue commitment that was not.
The record skill says that, before leaving an overdue commitment open, its evidence is looked for in the governing body's meeting material, and `ea-scan` repeats it. Ofelia was rerun on the Colombian control: no extra signal and the commitment met with its evidence.
the agent’s instructions · control office · Colombia · d11470ea
EA-8Fixed and verified
In the run that verified EA-7, Ofelia added to what is still unknown about a decision a fact the minutes already state: that it is decided at the next meeting.
The decision skill says `missing` holds only what the material does not answer, not what the documents already say. Ofelia was rerun on the Colombian control: no extra signal and 22 of 22 data points.
the agent’s instructions · · d11470ea
EA-9Fixed and verified
The batch's proposals carried no figures, and the regional office one had the same options as the vendor one: «carry on as today» and «change vendor». Ofelia said so in what is still unknown for each decision, and she was right; the key expected nothing to be missing.
Each proposal carries its two options, specific to the matter, with what each one costs, and says the offers are complete. Setup and processing were repeated on banking and on cooperatives: 50 of 50 and 35 of 35 signals, and 51 of 51 and 45 of 45 data points.
the test data · a bank’s president’s office · Colombia · 10bb31d7

How the engine was tested4 offices

Synthetic material from a bank’s president’s office (Colombia), a credit union’s general manager’s office (Ecuador), plus 2 control offices with no defects: 4 offices with their calendar, meetings and correspondence, and a key the engine never sees.

signals planted on purpose, each with its key

12 of 12

family signals planted at least once

control offices, where any signal is a failure

The engine raises every expected signal and none extra, and the gate that checks it runs on every change to the repository. The material also tests the rules of real operation: a clash that only appears after the clock change, an old calendar that gives no clashes, a draft in the minutes folder and an excluded folder.

What comes next

Round 3 with the agent, on all the material again.
The first use on a specific organisation’s documentation.
How many hours the agent give back is not measured yet. Until it is, we do not publish it.

A results page that only says what passed is advertising. What makes it auditable is what it says is not known yet.

Roadmap

The family grows in increments, each with its full test

Each increment is a version with its full test and its statistical analysis published, with the same metrics, so the evolution can be compared. Versions add up: the latest released one carries everything before it and the fixes for what its tests found.

StableIts evidence says so, not its number: in the latest run of each entity in its material, the lower bound of the 95% margin is 95% or more for signals and for data, and no control raised a signal. Each whole number has ten versions, from x.0 to x.9; then comes x+1.0.

0.12.0
Released
Released on 2026-10-27
Ofelia, built and tested with the full round with the agent
- Ofelia's commands, her skills and the engine: the .ics calendar with recurrences and the clock change, saved email, the governing bodies' meetings and commitments with Samuel's rules
- She prepares each decision with its options and evidence, without ranking or recommending
- Colombia and Ecuador, in a president's office and a general manager's office, and two control offices
Test
Round 1: Ofelia on the four offices, 14 of 14 signals and 76 of 78 data points, with one extra signal in a control; every defect it found, with its fix and its verification
Latest released
1.0.0
Released
Released on 2026-10-29
Carries everything before it, with its fixes
Travel, and each provider's exports
- Itineraries against the calendar
- The .ics that Outlook and Google Calendar export and Outlook's .msg email, each with its material: what really changes from one office to another, not the country
- The material seeds at least 73 signals, what a 95% floor with no misses needs (decision 0020), and the round with the agent runs again on all of it
Test
Round 2 with the agent on the four offices, each with its provider —Outlook or Google—: 85 of 85 signals and 144 of 146 data points on the first run, no signal in the controls; the defect it found, in the material, with its fix and its verification

The same roadmap lives in the repository, in families/criterio-ea/hoja-de-ruta.json.

How she works

Five steps and one boundary. The language model (LLM) extracts what only a written document holds; the code calculates everything else. It is generative AI plus a deterministic engine, applied to the executive’s office.

01
Your exports
The calendar as .ics, the emails saved as files and each meeting’s folder: notice, materials, notes and signed minutes. As they are, where they are.
She does not connect to the mailbox or the calendar.
The model extracts
02
Calendar and mail
The engine processes the calendar —recurrences, exceptions and time zones— and the headers of each email. What it cannot process it declares, with the reason.
An ambiguous event is declared, not guessed.
The model extracts
03
The record
One per meeting and one per email. The agreements, the commitments, the decisions with their options and what each email asks for, every item with its citation.
“Not found” is a valid answer.
The model extracts
04
The engine
Calendar clashes, materials by the configured days, pending minutes, every agreement against its owner and date, every commitment against its evidence, and the deadlines.
Deterministic and tested.
The code calculates
05
Signals
Only what crossed a threshold: what clashes, what is missing, what falls due and what is waiting for a reply. If nothing crossed one, it says nothing.
Silence is the feature.
The code calculates

No date, clash or deadline in a report comes from an estimate. And what is said nowhere is declared, not filled in.

Why this boundary matters →

Seven invariants that hold her up

She prepares; she does not recommend or decide

A decision’s options go in the order the documents bring them. The engine rejects a record that ranks them.

She never sends, schedules, accepts or moves anything

She writes drafts only in 90-borradores/, with «BORRADOR» in the name and in the text. A person sends.

She writes only in what is hers

Her state, her configuration and her drafts. She does not edit original minutes, calendars or emails.

A commitment is not met by saying so

It is met only with a document to back it. Each belongs to the minutes where it was born.

The model extracts, the code calculates

Every date, clash, deadline or count in a report comes from the engine. If the engine does not give it, it is not written.

She does not process what is excluded

Excluded folders are stated in every report, and nothing from them goes into a record.

Not published by default

Her report goes into Rostrum only if the office’s configuration says so.

The detail

For whoever wants to review all of it

The commands with their input, process and report; the signals the code calculates; the folder structure; the sources, and the links to the repository.

Ofelia’s commands10 commands

In order of importance. The first one sets up the configuration the others need.

0ea-setup
The configuration, the inventory and the governing bodies with their meetings
Input
The root folder. Questions: the executive and who assists them, the governing bodies in 00-referencia, the excluded folders, the thresholds —days before a meeting for the materials, days for the minutes, date changes that count, maximum age of the calendar—, whether it publishes to Rostrum and the terms
Process (calculated by the code)
Inventory of what is there; compares the folder with the recommended structure; creates, moves or renames nothing
Report
Configuration saved; inventory by folder; the excluded folders; the governing bodies with the meetings found
1ea-scan
The records of the meetings, the correspondence and the calendar
Input
The calendar in 10-agenda, each meeting in organos/, the correspondence in 20-correspondencia and the itineraries in 30-viajes (F-02, F-03)
Process (calculated by the code)
The code normalises the calendar —recurrences and time zones— and the emails; the language model (LLM) extracts from minutes, notes and emails the agreements, the commitments and what is being asked, each with its citation
Report
The new records and those that changed; what could not be processed and why
2ea-agenda
The executive's week: conflicts, trips against the calendar, meetings without materials and meetings without minutes
Input
The calendar record, the meeting records and the trip records
Process (calculated by the code)
Checks the executive's week against their meetings, their commitments and the flights of their trips; if the export is older than the threshold, it says so and computes no conflicts
Report
The conflicts, the meetings that fall during a flight or in the home city while travelling, the flights missing from the calendar, the meetings without materials and those without minutes, with the export date
3ea-prep
The meeting pack, with the record of each decision
Input
The governing body and the date of the next meeting; the record of the previous one
Process (calculated by the code)
Builds the agenda with what was left open, lists the materials missing from 20-material and prepares the record of each decision: the options the documents bring, the evidence for each with its citation, what is still unknown and the dates that set the deadline
Report
The meeting pack. It does not rank the options or say which one is best
4ea-minutes
The draft minutes, with each agreement and commitment cited
Input
The notes or the transcript in 30-notas
Process (calculated by the code)
The language model (LLM) extracts each agreement and commitment with its citation; the code flags those with no owner or no date
Report
The draft in 90-borradores, with «BORRADOR» in the name and in the text, and the list of what is missing to close it
5ea-commitments
The status of the executive commitments, by governing body and by owner
Input
The meeting records; the project records, if Samuel has them
Process (calculated by the code)
Using the commitment rules of the shared core, computes which are overdue without evidence, which have no date and which moved more than the threshold; project commitments are cited from Samuel's record, not recomputed
Report
The status of the executive commitments, by governing body and by owner
6ea-mail
The correspondence that needs a reply, with its drafts
Input
The correspondence records
Process (calculated by the code)
Computes what needs a reply and its deadline; for routine items, the language model (LLM) writes a draft reply
Report
What needs a reply and by when; the drafts in 90-borradores. It never sends
7ea-weekly
The weekly summary: what arrived, what is due and what still needs preparing
Input
The configuration and the records
Process (calculated by the code)
Gathers what arrived, what is due and what still needs preparing
Report
A single summary a week; not published to Rostrum unless the configuration says so
8ea-wake
What the office needs today; silent when nothing does
Input
The configuration and the records
Process (calculated by the code)
Decides what is due: the meetings entering the window, pending minutes, correspondence deadlines and a weekly review
Report
What ran and what it found; if nothing is due, it stays silent
9share-findings
A summary with no data to share, only if you say yes
Input
The local trail of this agent's runs, in .criterio/corridas/
Process (calculated by the code)
The code builds a summary with no data —the plugin and its version, each command with how many times it ran and its median duration, each signal by its code with how many times it came up— and always asks whether you want to share it; nothing is sent (decision 0025)
Report
The summary as is and, with a yes, the link to the repository's finding template, which the person opens

What the code calculates12 signals

12 signals. Each is raised with its date, its owner if the minutes say so and the citation of the document; the days, the counts and the calendar’s age are each office’s configuration.

Ofelia · 12

meeting_conflict
Two of the executive's meetings overlap in the exported calendar
meeting_without_material
Within the configured days before a governing-body meeting, its materials are not in the folder
meeting_without_minutes
The configured days after a meeting have passed and its signed minutes are not there
agreement_without_owner
An agreement in the minutes has no owner
agreement_without_date
An agreement in the minutes has no date
commitment_overdue
A commitment is overdue and no document supports it as done
commitment_rescheduled
A commitment was moved more times than configured
correspondence_unanswered
A saved email asks for a reply and its deadline passed with no saved reply
decision_deadline
A pending decision has a date that sets it within the configured days
meeting_during_flight
A meeting in the calendar falls during a flight in the executive's itinerary
meeting_while_away
An in-person meeting in the executive's home city falls while the itinerary has them travelling in another city
trip_not_in_agenda
A flight in the itinerary is not in the calendar: that time looks free

The folder structuredireccion/

Recommended, not mandatory: Ofelia processes the folder as it is. Setup says which file is out of place and where it would go, without creating, moving or renaming anything. It looks for the office folder, proposes it with its reason and, if you say yes, marks it with a visible file, _CRITERIO_DIRECCION.txt. Among your documents, besides that mark, she only writes her drafts, in 90-borradores/.

One folder per executive being assisted. Inside it, the office's reference files, the calendar, the correspondence, the drafts Ofelia prepares and one folder per meeting of each governing body.

direccion/
└── <ejecutivo>/
    ├── 00-referencia/
    ├── 10-agenda/
    ├── 20-correspondencia/
    ├── 30-viajes/
    ├── 90-borradores/
    └── organos/<órgano>/<AAAA-MM-DD>/
        ├── 10-convocatoria/
        ├── 20-material/
        ├── 30-notas/
        └── 40-acta/
estado-direccion/

<ejecutivo>/ · One executive's office

Folder	What goes there	Agent
`00-referencia/`	The governing bodies being followed —board, executive committee, board committees—, their members and their meeting calendar	Ofelia
`10-agenda/`	The calendar exports in .ics, with the export date in the name	Ofelia
`20-correspondencia/`	The emails saved as files, one per message: .eml, or Outlook's .msg	Ofelia
`30-viajes/`	The itinerary of each trip —the agency's, the airline ticket—, one per trip, with the departure date in the name	Ofelia
`90-borradores/`	The only place among the documents where Ofelia writes: draft minutes and draft replies, with «BORRADOR» in the name	Ofelia

organos/<órgano>/<AAAA-MM-DD>/ · One meeting of a governing body, with its date as the folder name

Folder	What goes there	Agent
`10-convocatoria/`	The notice of meeting and the agenda	Ofelia
`20-material/`	The materials sent to members before the meeting	Ofelia
`30-notas/`	The notes or transcript of the meeting	Ofelia
`40-acta/`	The signed minutes. Ofelia never files a draft here	Ofelia

estado-direccion/ · What Ofelia writes: the configuration, the record of each meeting, thread and export, and the reports. No person edits it, and Ofelia writes nowhere else except `90-borradores/`.

The sources3 of 3 verified

The role, from O*NET; the calendar and the email, from the standards that define their formats. Nothing is built on a source still to be verified.

F-01
O*NET · 43-6011.00 Executive Secretaries and Executive Administrative Assistants
Datos de 2026 (O*NET OnLine, sitio actualizado el 6 de octubre de 2026) · onetonline.org ↗
Verified
F-02
IETF · RFC 5545, Internet Calendaring and Scheduling Core Object Specification (iCalendar)
Septiembre de 2009, Proposed Standard; actualizada por las RFC 5546, 6868, 7529, 7953, 7986, 9073, 9074 y 9253 · rfc-editor.org ↗
Verified
F-03
IETF · RFC 5322, Internet Message Format
Octubre de 2008, Draft Standard; actualizada por la RFC 6854 · rfc-editor.org ↗
Verified

In the repository6 links

Installation, setup and terms

It installs in minutes. Before the first analysis, you accept the terms.

Three steps, and none of them asks you to edit a file. One instance per executive: if you assist two, each office has its own.

Step 1

Install

01Customize → Browse plugins → Personal.
02Press + → Add marketplace from GitHub.
03Enter josenanez/criterio.
04Install the agent for your role: Ofelia (Executive assistant).

To receive every new version, turn on auto-update once: in /plugin, Marketplaces → criterio → Enable auto-update. Without it, the installed version does not change on its own.

What it needs from you

A folder with the documentation, as it is. A messy folder is the normal case.
A paid Claude plan, and the desktop app if the documents live on your machine.
Fifteen minutes.

Step 2

Set up

Each agent comes with its own setup command. It looks at your folders, asks a few questions and shows you a first result on your own documents.

/criterio-assistant:ea-setup

1Which of the folders it finds is the office folder
2The executive, who assists them and the time zone of the calendar
3The governing bodies being followed
4The folders that are not processed
5Whether her report is published in Rostrum
6The terms

How it asks

One question at a time. Never a form.
Every question comes with a suggested answer, and “I don’t know” is a valid answer.
It does not ask what it can find out by looking at the folder.
It does not ask you to type a path: it searches for the folder, offers it with the reason and, if you say yes, marks it with a visible file so you recognise it at a glance.
Nobody edits the configuration by hand: if you want to change something, you say so in the conversation.

It does not schedule itself. It comes with the command a clock calls (ea-wake), and someone sets it once as a scheduled task. If your organisation does not want unattended runs, it is run by hand.

/criterio-assistant:ea-setupWhat Ofelia’s setup looks like

OfeliaI am Ofelia, Criterio’s executive assistant. I prepare the office’s work and say what clashes, what is missing and what is waiting for a reply; I send and decide nothing. I found a folder that looks like an office: direccion/presidencia, with the calendar exported on 2026-10-25, four meetings of two governing bodies and four emails. Is that the one?

An illustrative walk-through on the family’s test material: the president’s office of a test financial entity, with its calendar, four meetings and four emails. Nothing leaves your browser.

Step 3

The terms

Nobody reads a disclaimer in a repository. So the warning reaches the person who runs the agent and the person who later receives the document, in four layers that every agent implements.

1
One acceptance per version
Every version of the family is accepted again and leaves on your machine a receipt in Markdown and PDF, with the SHA-256 fingerprint of the terms and of the receipt itself. Until the one for the installed version is recorded, the agent answers questions but produces no full analysis. It never assumes it or infers it from you continuing to talk.
2
On every report
Every report carries a footer saying it is a draft, based on which documents, how many fields had no data and how many contradictions remain open. The document travels by email and reaches a committee: the warning travels with it.
3
At the start of every run
Before the first finding it says which records it loaded, when they were refreshed, and whether any is stale or missing.
4
In the legal notice
The full terms, the legal notice and the version register —what changed in each version, which terms govern it and their fingerprint— are published on this site, and every receipt points to them.

What you agree to, in plain words

You get working drafts ready for review, and every version arrives tested: its evidence is public.
Every data point carries its citation: whoever decides checks it in the original document in seconds.
It works with what is written; what was agreed outside the documents comes from your team.
Your documents are processed on the AI platform where you run it; your organisation decides which folders go in.
Warranty and liability: those of the Apache 2.0 licence.
Every version is accepted again and leaves a receipt in Markdown and PDF. If anyone modifies it, its SHA-256 fingerprint stops matching and it is void.

Terms version 1.3, of 2026-10-28, for version 1.0.1 of the family. Every new version of the family asks for acceptance again.

Legal notice and version register →

Apache 2.0

The method, the record schema, the code that computes and the acceptance criteria, in full and with no conditions. Use it inside your organisation without asking, adapt it, and build the capability you are missing: the agent for a function should be written by someone who knows the work.

What it does not do

It produces working drafts, not decisions.
It knows what was written, not what was said outside the documents.
Ofelia was tested with the engine and with the agent on 4 offices in Colombia and Ecuador; the latest round is round 2. Her first use on a specific executive’s office is the next step.

See the repository ↗

Frequently asked questions

What people usually ask when they reach the family

What it is

What does Ofelia do?

She prepares the work of the executive's office. She sets the week beside the meetings and the commitments, builds the pack for each governing body's next meeting with the record of each decision, drafts the minutes from the notes, follows the commitments in each set of minutes and says which email is waiting for a reply.

Does she replace whoever assists the executive?

No. She prepares and checks: which meetings clash, which meeting has no materials, which minutes are still unsigned, which agreement has no owner or date. What is accepted, sent and put first is always decided by a person.

Does she recommend what to decide?

No. Each decision arrives with the options the documents bring, in the order they bring them, with the evidence for each one, what is still unknown and the date that sets the deadline. The engine rejects a record that ranks the options or marks one as recommended.

What does she never do?

She does not send, schedule, accept or move anything. She does not edit original minutes, calendars or emails, does not declare a commitment met without a document to back it and does not evaluate a person or a team.

How it is used

Which documents does she process?

The ones the office exports: the calendar as .ics, the emails saved as files, and each meeting's notice, materials, notes and signed minutes. She does not connect to the mailbox or the calendar: a direct connection is a separate decision, with its own privacy review.

How do I organise the folder?

As it is: Ofelia processes it that way. If you start from scratch, the family recommends one folder per executive with its reference files, calendar, correspondence, drafts and one folder per meeting of each governing body. Setup looks for the office folder, proposes it and, if you say yes, marks it with a visible file, _CRITERIO_DIRECCION.txt. Among your documents, besides that mark, she only writes her drafts, in 90-borradores/.

How long until the first result?

Within the first fifteen minutes, ea-setup shows the calendar for the next two weeks with its clashes, the meetings without materials and those still without minutes.

Which countries does she work in?

Any. Ofelia processes no invoices or regulations, only the calendar, the minutes and the email, so the office's country is a data point, not a limit. What does change from one office to another is how its calendar and email provider exports: that is what gets tested next.

Where do I see what she found?

In each command's report, in her state folder. Her report is not published in Rostrum unless the configuration says so.

How it is tested

What data was it tested on?

On synthetic material from two countries —Colombia and Ecuador—: a president's office and a general manager's office with seeded defects, and one control office per country, with no defects at all, where any signal is a failure. Every signal is seeded at least once, and the material also tests the rules of real operation: a meeting in another time zone that only clashes after the clock change, an old calendar that gives no clashes, a draft put in 40-acta/ and an excluded folder.

How do you know the engine got it right?

The material carries a key with what was planted, and the engine never sees it. The test compares every signal by its name and its key: an extra one counts the same as a missing one. The gate that checks it runs on every change to the repository.

Is the family tested yet?

The engine is, against the key of the four offices. The agent's extraction —the agreements, commitments and decisions in each set of minutes, and what each email asks for— is tested in the round with the agent on the same four offices, published with every output, its cost and its grade. Nothing has run yet on a real executive's office.

Data and privacy

Do the calendar and the emails leave my organisation?

They are processed on the AI platform where the agent runs, like any conversation with it. The plugin does not connect to the internet or send us anything. The executive's office is among the most sensitive things an organisation has: that is why she processes exports, not accounts, and respects the folders you exclude.

What is kept and where?

On your computer: the meeting and correspondence records, the reports, the drafts, the log of each run and the receipt for accepting the terms, which each version asks for again.

The same answers live in the repository, in families/criterio-ea/PREGUNTAS.md.

Support the work

If Criterio created value for you, help keep it moving.

Criterio remains open source. A voluntary contribution helps fund testing, documentation and the next capabilities without changing access to the software.

This is a voluntary contribution. It does not unlock features, purchase consulting services or create an advisory relationship.

Support Criterio

Choose an amount and how you want to contribute.

Choose an amount

Where are you paying from?

Choose your country to see the payment methods available to you.

dLocal Go currently covers Latin America, Indonesia, Malaysia, Kenya and Nigeria. Global coverage will be added separately.

The idea

What the governing body agreed was always written down. Nobody had set it beside the executive’s week.

An assistant that processes the calendar and the minutes does not hand you a control you never built. She shows you, every week, what clashes, which agreement has no owner and which commitment moved three times, and leaves the decision where it was: with a person.

Principles

Approach: Prepare, without recommending.
Commitment: Generating, sharing and preserving knowledge is a professional obligation.
What it is not: It does not replace whoever assists the executive or the board secretary: it does not send, schedule, accept or move anything, and does not prioritise for the executive.
Licence: Apache 2.0.
What comes next: Travel —itineraries against the calendar— and each calendar and email provider’s exports, and then deployment in a real office.

Legal notice and version register →

José Ñáñez