← Criterio · PMO family

Legal notice · Criterio

Legal notice and version register

What you accept when you use the Criterio agent family, how it is recorded for every version, and the register of every version with the terms that govern it and their fingerprint.

Current version 0.5.0 · Terms 1.1 of 2026-10-15

José Ñáñez
José ÑáñezTechnology Advisor · Board Member
Published October 15, 20266 min read

What you agree to when you use Criterio

What you get
Working drafts ready for review: each project’s record, the portfolio report, the minutes, the committee pack. Every data point carries the citation of the document it came from, and decisions stay with your team.
Certified on every version
Every version goes through an internal certification before it is published: automated tests of the code on every change, and rounds in which the three agents run all their commands on synthetic test data built from real projects in financial entities, retail and mining. Results and fixed defects are published in the test evidence.
You decide with the evidence in view
Because every data point comes with its citation, whoever signs, reports or escalates checks it in the original document in seconds, instead of redoing the work.
It works with what is written
It processes the documents you point it to and says what is written and what is not. What was agreed outside them comes from your team, and the agent picks it up as soon as it is written down.
Your data
Processed on the AI platform where you run it, under its terms of use. Your organisation decides which folders and documents go in.
Open licence
Apache 2.0: use it, adapt it and extend it inside your organisation without asking. Warranty and liability are governed by that licence, sections 7 and 8.
Trademark
“Criterio” identifies this agent family; to use the mark on a derivative product, write to the maintainer. It is an independent project that runs on Claude, by Anthropic.

One acceptance per version

Every version of the family asks for the terms to be accepted again, even when their text did not change. Installing or updating requires a new acceptance, and earlier ones are kept: the dated succession of acceptances is the trail.

  1. 1

    The agent shows the summary

    The “In short” section of the terms, as written, with the link to this notice. It asks for an explicit yes and the name of whoever accepts. It never assumes it or infers it from the conversation going on.

  2. 2

    It leaves a receipt that is yours

    In .criterio/terminos/, in Markdown and in PDF: name, date, family version, the terms’ version and SHA-256, that version’s register entry, and the full text accepted.

  3. 3

    It records each receipt’s fingerprint

    In the configuration, in a .sha256 file next to it and in the aceptaciones.json log, where every acceptance carries the fingerprint of the previous one.

  4. 4

    And the gate is code

    No command produces analysis or reports if the acceptance is for another version, another text, or if the receipt changed after it was recorded.

Integrity: SHA-256

Every receipt keeps its integrity and may not be modified. Its SHA-256 fingerprint (SHA-2, 256 bits) is a 64-character figure that changes completely with any change to the file, however small. A receipt whose fingerprint does not match the recorded one is void as a record. The same holds for the terms and for every entry of the version register.

How to check it, with nothing to install

macOS or Linux, in the receipt’s foldershasum -a 256 -c aceptacion-criterio-portfolio-0.5.0-AAAA-MM-DD.sha256

Windowscertutil -hashfile aceptacion-criterio-portfolio-0.5.0-AAAA-MM-DD.md SHA256

And the terms’ fingerprint, against the one published hereshasum -a 256 TERMS.md

The current terms

TERMS.es.md
Version 1.1 · 2026-10-15 · SHA-256 d31e6b36110416181cb7d8dd69726f1c27e7f8d06b28a48116cddc43213a7bf0
TERMS.md
Version 1.1 · 2026-10-15 · SHA-256 baf6ad76bb5e9539b925b378da24ea8f20f3b567302b90b2ca7f3b56691419c7
Read the full terms

By installing, deploying, testing or running Criterio, you accept these terms. If you do not accept them, do not install it.

1. Not advice; every version is certified before it is published

Criterio produces working drafts. It is not advice and creates no professional relationship of any kind between you and the maintainer or any contributor.

Every version goes through an internal certification before it is published: automated tests of the code on every change, and rounds in which the three agents run all their commands on synthetic test data, built from real projects in financial entities, retail and mining, with no data from any organisation. What each agent produces is compared with an answer key, and the results —with their confidence margin, the defects found and their fix— are published in the test evidence and the legal notice: https://www.josenanez.com/agents/criterio-pmo.

2. Verification is yours

You are responsible for verifying every output before using it to decide, sign, report, escalate or advise. The citations exist so that verification is possible; they are not a substitute for it.

3. What it can and cannot know

Its input is the documents you point it at. It does not know what was decided outside them. An absent finding is not evidence that nothing is wrong.

4. Your data

Documents you process are handled by the AI platform you run this on, under that platform's terms, not only on your machine. Confirm that this is admissible under your policies, your contracts and the applicable data protection law before processing confidential or personal material. That assessment is yours.

Do not send this project any client documents, real personal data, or confidential material. Contributions containing them will be rejected.

5. Warranty and liability

Governed by the Apache 2.0 licence, sections 7 and 8.

6. Contributions

Contributions are licensed under Apache 2.0 by the act of submitting them. By contributing you state that you wrote the content or have the right to submit it, and that it contains no confidential or client material.

Contributors are credited by name. Credit records who wrote something; it is not a warranty.

7. Trademarks

Apache 2.0 grants no trademark rights. "Criterio" and the maintainer's name may not be used to endorse or promote derivative products without written permission. Anthropic's marks are its own; this project is not affiliated with, endorsed by, or sponsored by Anthropic.

8. How acceptance is recorded

One acceptance per version. Every version of the agent family asks you to accept these terms, even when their text did not change: installing Criterio or updating it to a new version requires a new acceptance. Until the acceptance for the installed version is recorded, the plugin answers questions but produces no analysis and no report. It never assumes it, never infers it from you continuing the conversation, and never records it without an explicit yes.

A receipt that is yours. On acceptance, the plugin leaves on your machine, in .criterio/terminos/, a Markdown receipt and a PDF receipt with your name, the date, the family version, the version of these terms, their SHA-256 fingerprint and the version-register entry, followed by the full text you accepted. Earlier receipts are kept: the succession of acceptances is the trail. The technical detail is in docs/acceptance.md, in the repository.

Integrity. Every receipt keeps its integrity and may not be modified. Its SHA-256 fingerprint (SHA-2, 256 bits) is recorded in the configuration, in the acceptance log and in a .sha256 file next to it; any change, however small, produces another fingerprint and voids it as a record. The same holds for these terms: their fingerprint is published with every version.

Legal notice and version register. The legal notice of the agent family and the version register —what changed in each version, which terms govern it and their fingerprint— are published at https://www.josenanez.com/agents/criterio-pmo/legal. Every register entry carries the fingerprint of the previous one, so an altered or removed entry shows.

Every report the plugin generates carries the disclaimer and the state of the records it used, so the warning travels with the document rather than staying in this repository.

9. Changes to these terms

These terms are versioned. A change bumps the version and the date at the top of this file and enters the version register with its fingerprint. Since every family version is accepted again, a change to the terms reaches whoever uses Criterio on the next update.

In short

This is what the plugin shows you before asking you to accept:

Criterio produces working drafts, not decisions or advice. It processes the documents you point it to and says what they show; it does not know what was said outside them. It can be wrong, which is why every data point comes with a citation to the document it came from: verification is yours. Your documents are processed on the AI platform's infrastructure, not only on your machine. Every version is certified before it is published; warranty and liability: Apache 2.0 licence. Every version is accepted again and leaves a receipt in Markdown and PDF with its SHA-256 fingerprint. Full terms and legal notice: https://www.josenanez.com/agents/criterio-pmo/legal

Full text of the licence: LICENSE, at the root of the repository. Plain-language limits: DISCLAIMER.md. Legal notice and version register: https://www.josenanez.com/agents/criterio-pmo/legal

Version register

Like a patent register: every version leaves an entry that is never deleted or rewritten, with its date, what changed, the terms that govern it with their fingerprint, and the fingerprint of what each agent does. Every entry carries the fingerprint of the previous one, so an altered or removed entry breaks the chain. The chain is checked in the repository on every change and again when this page is published.

Each entry records the commit where the version was born. From 0.3.9 it also records its GitHub tag, created on the commit that contains the entry. Before that, the v0.3.6 tag marks a later commit of the same version, and v0.3.8 the commit that registered it.

  1. 0.5.0Current

    2026-10-18 · On commit 065b50c5 · Tag v0.5.0

    Highlights

    • Versión de lanzamiento de la familia de gobierno de proyectos.
    • El contraste entre la ficha del gerente y la de la PMO lee el producto con su regla: «No aplica» es un campo vacío, no un producto.
    4 changes recorded in the repository
    • The manager-PMO contrast reads the product with its own rule: «No aplica» is empty, not a product
    • The key reads «No aplica» in the product as empty, as the schema says (D057)
    • Round 9 on 0.4.0: 148/148 contracts, Samuel 108/108, Alba 128/128, Rostrum 2170/2170, Vera 266/266 found and 266/267 right
    • Launch notes for 0.4.0, in Spanish and English, with round 9 as the measured result and what is not known yet

    How it was accepted: una aceptación por versión, con comprobante en Markdown y PDF, huella SHA-256 de los términos y del comprobante, y bitácora encadenada

    Terms

    1.1 · 2026-10-15

    TERMS.es.md d31e6b3611041618…

    TERMS.md baf6ad76bb5e9539…

    Each agent’s fingerprint

    Vera 17a487857456

    Alba 469e3bf2a2a1

    Samuel a8273f7a814c

    Chain

    Previous 81fed035a2e6e0c0…

    This entry a455ee96c5153980…

  2. 0.4.0

    2026-10-17 · On commit 7f3984f7 · Tag v0.4.0

    Highlights

    • Primera versión pública de la familia de gobierno de proyectos: Vera, Samuel, Alba y Rostrum, 37 comandos, probados en ocho rondas sobre datos de prueba de cuatro industrias.
    • El informe del portafolio va siempre a la carpeta que Rostrum sirve, contada desde la raíz del espacio y no desde donde esté el agente.
    • El manual de los 37 comandos se genera desde el README y el contrato de cada plugin, y la verificación falla si deja de coincidir.
    • Las páginas de resultados y de evidencia leen las rondas de punta a punta.
    7 changes recorded in the repository
    • The command manual, generated from each plugin's README table and contratos.json, with a gate that fails when it drifts
    • The results and evidence pages say what the end-to-end rounds already proved
    • A verified assumption comes with its verification document in the product folder
    • Round 7 on 0.3.13: 148/148 contracts, Vera 280/280, Samuel 108/108, Alba 140/140 found and 140/141 right, Rostrum 2190/2190
    • The report folder is counted from the workspace root, not from wherever the shell stands
    • Mining progress notes no longer carry a random vendor delivery the key does not model (D055, the one D022 missed)
    • Round 8 on 0.3.13: Samuel 108/108, Alba 149/149 with no extra alert, Vera 253/253 found and 253/254 right, Rostrum 2041/2056, 147/148 contracts

    How it was accepted: una aceptación por versión, con comprobante en Markdown y PDF, huella SHA-256 de los términos y del comprobante, y bitácora encadenada

    Terms

    1.1 · 2026-10-15

    TERMS.es.md d31e6b3611041618…

    TERMS.md baf6ad76bb5e9539…

    Each agent’s fingerprint

    Vera f3486e563e41

    Alba 1a56b70d7346

    Samuel 3ebf817c8eac

    Chain

    Previous 95f71e8af113f999…

    This entry 81fed035a2e6e0c0…

  3. 0.3.13

    2026-10-17 · On commit fe7e4b2e · Tag v0.3.13

    Highlights

    • El caché de texto tiene un solo lugar, <estado>/cache/texto, y texto.py rechaza cualquier otro.
    • La página de una corrida cabe en un teléfono: su bloque se desplaza en vez de ensanchar la página.
    • compute devuelve record_issues cuando una ficha guarda como reprogramación la primera fecha de un compromiso sin fecha, y los comandos de Samuel la corrigen antes de terminar.
    4 changes recorded in the repository
    • The text cache has one place, now enforced by texto.py; a run page's block scrolls on a phone instead of widening it
    • compute returns record_issues when a record lists the first date of an undated commitment as a reschedule, and Samuel's commands fix the record before finishing
    • A verified assumption in the generated definition says what verified it
    • Round 6 on 0.3.12: Vera 266/266 with no false alert, Samuel 107/108, Alba 135/135 found and 135/136 right, Rostrum 2173/2174, 145/148 contracts

    How it was accepted: una aceptación por versión, con comprobante en Markdown y PDF, huella SHA-256 de los términos y del comprobante, y bitácora encadenada

    Terms

    1.1 · 2026-10-15

    TERMS.es.md d31e6b3611041618…

    TERMS.md baf6ad76bb5e9539…

    Each agent’s fingerprint

    Vera 70192c510338

    Alba 1a56b70d7346

    Samuel 3ebf817c8eac

    Chain

    Previous 145e91d6a6f363d0…

    This entry 95f71e8af113f999…

  4. 0.3.12

    2026-10-16 · On commit 46aa2bb8 · Tag v0.3.12

    Highlights

    • Vera y Samuel se presentan por lo que hacen: procesan la documentación que ya tienes.
    • Samuel publica como fecha de cierre la vigente, la del cronograma más reciente: la misma que contrasta la PMO.
    • El ejemplo de project-record guarda en value el documento más reciente, como dice su propia regla.
    • Un compromiso cumplido con acta ya no suena como reprogramado.
    6 changes recorded in the repository
    • Release 0.3.11, entered in the version register
    • Round 5 on 0.3.11: 148 of 148 contracts, Alba 150/150, Rostrum 2155/2155, Samuel 102/104, Vera 223/228
    • A commitment met with a receipt no longer sounds as rescheduled
    • Defects: D040, D041 and D043 to D045 verified on round 5; D046 found and fixed
    • The key models the manager-PMO contrast from the published record, and the charter closes where the schedule does
    • Defects: D012 fixed in the key; D047 (material) and D048 (instructions) registered and fixed

    How it was accepted: una aceptación por versión, con comprobante en Markdown y PDF, huella SHA-256 de los términos y del comprobante, y bitácora encadenada

    Terms

    1.1 · 2026-10-15

    TERMS.es.md d31e6b3611041618…

    TERMS.md baf6ad76bb5e9539…

    Each agent’s fingerprint

    Vera e22c87c17ff1

    Alba 056db146457e

    Samuel 662d43900335

    Chain

    Previous 3a37b8e5acfa45a0…

    This entry 145e91d6a6f363d0…

  5. 0.3.11

    2026-10-16 · On commit 9a21b05 · Tag v0.3.11

    Highlights

    • Alba: la evidencia de un requerimiento es la entrevista de donde viene la demanda, no el acta del comité que lo acepta; lo dice el comando que extrae.
    • Samuel: fechar un compromiso prometido «por definir» no es reprogramarlo, en sus comandos y en la aritmética.
    • Rostrum abre las páginas de productos con nombre —tildes y espacios— y codifica cada tramo de sus rutas.
    • El sello de Vera revisa solo sus propias citas; una cita es una sola ruta.
    • not_found es un estado, nunca un valor: un requerimiento con el doliente escrito así no tiene doliente.
    7 changes recorded in the repository
    • not_found is a state, never a value: a requirement whose owner is written as "not_found" has no owner
    • Round 3 on 0.3.9: Vera 252/256, Alba 142/143 with no false positive, Rostrum 1949/1964, Samuel 80/104
    • product-setup says where requirement evidence comes from: the interview, not the committee act that accepts it
    • Rostrum encodes each path segment, and the end-to-end check follows links as a browser does
    • Dating an undated commitment is not rescheduling it, now in Samuel's commands and in the arithmetic
    • Rostrum opens cases with a name, Vera's seal is hers alone, and a citation is one path
    • Round 4 on 0.3.10: Samuel 100/104, Vera 228/231, Rostrum 2128/2132, Alba 135/146 with no false alert

    How it was accepted: una aceptación por versión, con comprobante en Markdown y PDF, huella SHA-256 de los términos y del comprobante, y bitácora encadenada

    Terms

    1.1 · 2026-10-15

    TERMS.es.md d31e6b3611041618…

    TERMS.md baf6ad76bb5e9539…

    Each agent’s fingerprint

    Vera 4ac579180f6b

    Alba 36d648b9d02c

    Samuel 398b4b498fe1

    Chain

    Previous 45caaf940f463b11…

    This entry 3a37b8e5acfa45a0…

  6. 0.3.10

    2026-10-15 · On commit 7d48c2a · Tag v0.3.10

    Highlights

    • Samuel lee todas las minutas del proyecto en orden al configurarse, para que la ficha traiga el historial de cada compromiso: cuántas veces se movió y qué se cerró con acta.
    • Ponerle fecha a un compromiso que no la tenía no es reprogramarlo.
    • El informe tiene un solo lugar, la carpeta que Rostrum sirve; el script rechaza otra.
    • Rostrum: las rutas largas dentro de código se parten en un teléfono.
    • pm-wake declara la ficha que escribe en su barrido y no deja copias de respaldo.
    5 changes recorded in the repository
    • Rostrum's figure on round 2 with 0.3.8: 1742 of 2182 checks (80%); the round summary carries it per industry
    • pm-setup reads every meeting minute in order, so the commitment register carries its history
    • Long paths in code wrap on a phone instead of pushing the run page wider than the screen
    • The report has one place, paths.reports, which is what Rostrum serves
    • Dating an undated commitment is not rescheduling it; pm-wake declares the record it writes and leaves no backup copies

    How it was accepted: una aceptación por versión, con comprobante en Markdown y PDF, huella SHA-256 de los términos y del comprobante, y bitácora encadenada

    Terms

    1.1 · 2026-10-15

    TERMS.es.md d31e6b3611041618…

    TERMS.md baf6ad76bb5e9539…

    Each agent’s fingerprint

    Vera 832009d541b9

    Alba b4e96d9a570c

    Samuel 2a7fdf645034

    Chain

    Previous f742387fc01a65fe…

    This entry 45caaf940f463b11…

  7. 0.3.9

    2026-10-15 · On commit aefd53d · Tag v0.3.9

    Highlights

    • Una sola regla por campo: el proveedor declarado entregado sin acta se registra como declarado, con la evidencia vacía, en los dos skills de Vera.
    • Samuel: la promesa original nunca es una reprogramación, también en pm-minutes y pm-commitments.
    • Alba: el acta que registra la decisión va en su campo, aunque sea una revisión posterior, y el acta del comité no es evidencia de demanda.
    • sellar rechaza una ficha con citas a documentos que no existen.
    • El caché de texto tiene un solo lugar, <estado>/cache/texto/.
    • Rostrum: ningún enlace del menú lleva a un error, cada campo y cada señal se nombran en castellano y ninguna página se sale de la pantalla de un teléfono.
    9 changes recorded in the repository
    • Every register entry carries its tag, and the tag sits on the commit that holds the entry
    • ronda.py: the test session accepts the terms in force for the version, and records it by name
    • Round 2 on 0.3.8: 148 of 148 commands, Vera 223/230, Alba from 0 to 38 of 43
    • Round 2 fixes: one rule per field, citations that resolve, and a key that counts what is visible
    • Defects D022 to D029 point to their fix, 7b5ab31; D026 and D029 verified
    • Rostrum tested end to end, and what that found: a menu link to an error, raw field paths, signal keys and tables wider than a phone
    • Defects D030 to D034: Rostrum, found by the end-to-end check, fixed in fa65257 and verified on round 2
    • Samples large enough to measure Samuel and Alba: about a hundred graded cases each per round
    • Rostrum gets its own figure: checks that pass out of checks made, phone and desktop included

    How it was accepted: una aceptación por versión, con comprobante en Markdown y PDF, huella SHA-256 de los términos y del comprobante, y bitácora encadenada

    Terms

    1.1 · 2026-10-15

    TERMS.es.md d31e6b3611041618…

    TERMS.md baf6ad76bb5e9539…

    Each agent’s fingerprint

    Vera e3deeb24e5ae

    Alba 09509969b517

    Samuel fcdc5c8fb4dd

    Chain

    Previous a9f5f18ec3113c32…

    This entry f742387fc01a65fe…

  8. 0.3.8

    2026-10-15 · On commit 46c9e65

    Highlights

    • Una aceptación de términos por versión, con comprobante en Markdown y PDF, su huella SHA-256 y una bitácora encadenada; la puerta es código.
    • Registro de versiones de la familia, encadenado por huellas, que se publica en la nota legal del portal.
    • Términos 1.1: certificación interna de cada versión antes de publicarse, aceptación por versión, comprobantes e integridad; garantía y responsabilidad se remiten a la licencia Apache 2.0.
    • Alba construye la ficha de su producto y su registro de requerimientos desde lo escrito, y cada agente guarda su estado en su propia carpeta.
    • El compromiso reprogramado guarda la promesa original aparte de sus reprogramaciones.
    • La regresión del motor corre en cada verificación del código.
    • Rostrum: «No aplica» deja de ser un producto, las tablas anchas se desplazan dentro de su bloque y un campo no encontrado se lee como tal.
    23 changes recorded in the repository
    • defectos.json: the commits that fix the four round-1 defects already corrected
    • A round summary for the portal, computed from the evidence
    • Round 1, cooperatives: 37 of 37, Vera 60/60, and a commitment counted twice
    • A rescheduled commitment: the original promise is not one of its reschedules
    • defectos.json: D014 fixed in 5e81ef7
    • commitment_rescheduled carries the original date too; gates green again
    • Round 1, retail: 37 of 37, Vera 36/37, Samuel 3/3; graders read each agent's state from its config
    • defectos.json: D015, the grader read a fixed state path
    • Round 1 closed: mining 37 of 37, Vera 37/39; four industries, 148 commands, 186/190
    • Origin of the round-1 retail and mining errors: the key, D012
    • docs/pruebas: 29 of 29 gates, 672 checks, round 1 closed
    • «No aplica» is an empty product, and wide tables scroll inside their block
    • defectos.json: D016 and D017, found in Rostrum on the mining round
    • A field not found reads as not found, even when the record copied the state into the value
    • defectos.json: D018
    • The engine's five-week regression runs on every verification
    • Regression run of 15 October on c97cd8e: five of five cuts match the key
    • docs/pruebas: 30 gates with the engine regression
    • Round summary counts the documents each industry handed the agents, and its projects
    • Terms: one acceptance per version, a receipt in Markdown and PDF with its SHA-256, and a version register
    • defectos.json: D019-D021, the terms gate and where the terms live
    • The PDF receipt reads each row as label: value
    • Every version is certified before it is published; warranty and liability are Apache 2.0's

    How it was accepted: una aceptación por versión, con comprobante en Markdown y PDF, huella SHA-256 de los términos y del comprobante, y bitácora encadenada

    Terms

    1.1 · 2026-10-15

    TERMS.es.md d31e6b3611041618…

    TERMS.md baf6ad76bb5e9539…

    Each agent’s fingerprint

    Vera b86b6702428c

    Alba 88392eb8037a

    Samuel 04ad5e8c12b1

    Chain

    Previous d8af32b4c5a1b92a…

    This entry a9f5f18ec3113c32…

  9. 0.3.7

    2026-10-14 · Commit db80a49

    4 changes recorded in the repository
    • A test round is the three agents, all 37 commands, in order, in one industry
    • ronda.py: the commitment Samuel's notes reschedule has to have a date
    • Round 1, banks: 37 of 37 commands, and what they found
    • Alba builds her product record and her requirements register from what is written

    How it was accepted: versión de los términos, fecha y nombre en la configuración; sin huella ni comprobante

    Terms

    1.0 · 2026-09-18

    TERMS.es.md 1248a5e1aea7b80b…

    TERMS.md c91a767ff5235a50…

    Each agent’s fingerprint

    Vera 1d1f62085fd2

    Alba 4f9ab506a77f

    Samuel 530bdb5b7a17

    Chain

    Previous 2364a6d8592f5c3e…

    This entry d8af32b4c5a1b92a…

  10. 0.3.6

    2026-10-14 · Commit 8c84264

    3 changes recorded in the repository
    • Three industries and three formats: the material now arrives as it does in real life
    • Test data by industry, not by company; and every agent figure with its counts, interval and origin
    • First held-out runs in four environments, and what they found in the material

    How it was accepted: versión de los términos, fecha y nombre en la configuración; sin huella ni comprobante

    Terms

    1.0 · 2026-09-18

    TERMS.es.md 1248a5e1aea7b80b…

    TERMS.md c91a767ff5235a50…

    Each agent’s fingerprint

    Vera 1d1f62085fd2

    Alba 6e2684900e33

    Samuel 530bdb5b7a17

    Chain

    Previous 2d48d5e34c6ea74c…

    This entry 2364a6d8592f5c3e…

  11. 0.3.5

    2026-10-14 · Commit 9fd41a8

    4 changes recorded in the repository
    • Cierre de la prueba longitudinal de cinco días
    • What the family stands for, in its header; and the run trail carries no local paths
    • Las figuras con los robots del portal, y la familia animada
    • First model run, first fixes: silence from the files on disk, progress against a range

    How it was accepted: versión de los términos, fecha y nombre en la configuración; sin huella ni comprobante

    Terms

    1.0 · 2026-09-18

    TERMS.es.md 1248a5e1aea7b80b…

    TERMS.md c91a767ff5235a50…

    Each agent’s fingerprint

    Vera 3fc31754bdac

    Alba c4ac10179333

    Samuel 572dc3ab9779

    Chain

    Previous 2ec8a44afb174a6c…

    This entry 2d48d5e34c6ea74c…

  12. 0.3.4

    2026-10-02 · Commit 2fbbee5

    5 changes recorded in the repository
    • Ready to be public: a security policy, an honest status line, and no test machinery
    • Dependabot watches the only third-party code that runs here: the workflow's actions
    • Results pages point at a commit that exists in the public history
    • The workflow's actions are pinned to their commit, as the repository now requires
    • The robots, in the READMEs and in the server

    How it was accepted: versión de los términos, fecha y nombre en la configuración; sin huella ni comprobante

    Terms

    1.0 · 2026-09-18

    TERMS.es.md 1248a5e1aea7b80b…

    TERMS.md c91a767ff5235a50…

    Each agent’s fingerprint

    Vera 498f6425e69e

    Alba 84f011bac31e

    Samuel b97a158128f1

    Chain

    Previous 608addad44a75ddd…

    This entry 2ec8a44afb174a6c…

  13. 0.3.3

    2026-10-01 · Commit 661d8ea

    1 change recorded in the repository
    • Samuel's setup inherits what Vera's taught, and its test corpus

    How it was accepted: versión de los términos, fecha y nombre en la configuración; sin huella ni comprobante

    Terms

    1.0 · 2026-09-18

    TERMS.es.md 1248a5e1aea7b80b…

    TERMS.md c91a767ff5235a50…

    Each agent’s fingerprint

    Vera a076ad4bdd4e

    Alba 84f011bac31e

    Samuel b97a158128f1

    Chain

    Previous bff70225b0181c5c…

    This entry 608addad44a75ddd…

  14. 0.3.2

    2026-10-01 · Commit 3b0133d

    2 changes recorded in the repository
    • Move the marketplace to josenanez/criterio
    • An overdue commitment is arithmetic, not a label

    How it was accepted: versión de los términos, fecha y nombre en la configuración; sin huella ni comprobante

    Terms

    1.0 · 2026-09-18

    TERMS.es.md 1248a5e1aea7b80b…

    TERMS.md c91a767ff5235a50…

    Each agent’s fingerprint

    Vera a076ad4bdd4e

    Alba 84f011bac31e

    Samuel 2d3f11147860

    Chain

    Previous 18cdd19fa969bc6f…

    This entry bff70225b0181c5c…

  15. 0.3.1

    2026-09-30 · Commit d48f84c

    1 change recorded in the repository
    • What a script can read from a table, the script reads; subagents are blocked, not asked

    How it was accepted: versión de los términos, fecha y nombre en la configuración; sin huella ni comprobante

    Terms

    1.0 · 2026-09-18

    TERMS.es.md 1248a5e1aea7b80b…

    TERMS.md c91a767ff5235a50…

    Each agent’s fingerprint

    Vera 05b49736d953

    Alba 1a6e28f2fbbd

    Samuel 22a1cdf829be

    Chain

    Previous 74d7c5e493c04aeb…

    This entry 18cdd19fa969bc6f…

  16. 0.3.0

    2026-09-30 · Commit bfd9fd1

    14 changes recorded in the repository
    • The configuration has one address, and every command names it
    • The tree reads at a glance: plain names, a line per group, and a phone layout
    • The page has a real layout: a menu column with its own gutter, and content with margins
    • The menu is for the reader; the catalogue moves to each agent's page
    • What is declared and what is proven are two fields, and the reading is complete before it is written
    • The reading plan is computed, the hashes are sealed, and the parallelism is counted
    • A command runs without asking at every step
    • The inventory comes from the script, not from find > /tmp
    • A record is sealed only if this run wrote it
    • Every command and skill has a contract, and the contract is checked against the code
    • Phase 2 harness: a six-project corpus that covers every signal, and its grader
    • No parallel subagents in any command, not only in the scan
    • Setup writes what it shows, where the other commands look for it
    • Every run says which copy of the plugin ran, and 0.3.0 forces a fresh copy

    How it was accepted: versión de los términos, fecha y nombre en la configuración; sin huella ni comprobante

    Terms

    1.0 · 2026-09-18

    TERMS.es.md 1248a5e1aea7b80b…

    TERMS.md c91a767ff5235a50…

    Each agent’s fingerprint

    Vera 2b5aafbe3704

    Alba 8169d8707a25

    Samuel bd5eb63acfaa

    Chain

    Previous 9a9f8b61fab12571…

    This entry 74d7c5e493c04aeb…

  17. 0.2.0

    2026-09-30 · Commit 2a201c8

    84 changes recorded in the repository
    • Presentación como market de capacidades, y comando de instalación
    • Portada orientada al negocio, con cifras de mercado citadas
    • Calcular lo que el esquema ya declaraba y la prosa ya prometía
    • Las hojas de los tres agentes: qué hacen, qué no, y qué es de las personas
    • La clase C deja de evaluar riesgos, y cada función declara qué entra y qué sale
    • Portafolio sintético con respuestas conocidas, y seis límites que destapó
    • El índice de documentos, y cuatro de los seis límites cerrados
    • Cuatro skills y cuatro comandos: la capacidad PMO queda completa en A y en B
    • El documento a texto, sin dependencias, y la hoja del PMO consolidada
    • Un dueño por cosa: se borran las copias, y aparece una señal que faltaba
    • Se borra capabilities/: cuatro puertas para una capacidad eran tres de más
    • La instalación vuelve, y la política de valor queda escrita y verificada
    • Tres emblemas en la página central, y la familia PMO con sus agentes
    • El agente deja de esperar a que lo llamen, y ocho piezas en dos idiomas
    • criterio-pmo en los dos idiomas, y el chequeo que lo sostiene
    • El estado deja de parecer incompleto donde no lo está
    • Plomada, Escuadra y Compás: los agentes tienen nombre
    • El informe: el mismo dato, dos autoridades
    • El servidor: el informe, para quien no abre una carpeta
    • Un portal, no una carpeta de informes: PMO, proyectos y productos
    • La página del servidor, con el portal fotografiado
    • Atril: el servidor tiene nombre, y el nombre dice qué no hace
    • Escuadra: dos fichas que nunca se fusionan, y dos plugins
    • criterio-pm existe, y la regla que impide que las copias se separen
    • Los ocho skills del método viajan con Escuadra
    • Plumb, Bevel, Caliper, Rostrum: nombres que se venden fuera
    • Vera, Samuel y Alba: nombres de persona, porque extienden personas
    • El corpus de Samuel: un proyecto visto desde adentro
    • Samuel abre sus puertas: setup, compromisos y publicar
    • pm_vs_pmo: dónde el gerente y la PMO no leyeron lo mismo
    • Una sola puerta para verificarlo todo
    • Samuel cierra el ciclo de la reunión: agenda, acta e informe
    • Alba abre sus puertas: el registro de requerimiento y sus siete comandos
    • La página de resultados sale de correr las puertas, no de escribirlas
    • La última decisión de esquema queda cerrada: el registro de requerimiento
    • Los tres agentes dejan de aparecer en construcción, empezando por la figura
    • Samuel y Alba dejan de esperar a que los llamen
    • Las hojas de los agentes entran a la familia, y la familia tiene página
    • Las tablas A y B de los tres agentes quedan sin filas abiertas
    • La explicación de cada agente entra a su README, y sobran cinco páginas
    • Las capturas del portal decían Plomada, y ahora se sabe cuándo envejecen
    • La página de la familia muestra a los tres, y sin dibujos en ASCII
    • Los tres README de plugin son gemelos, y la familia vive en la raíz
    • La familia vuelve a criterio-pmo, y cada agente enlaza sus pruebas
    • La familia y Vera dejan de ser la misma página
    • Las tres páginas de agente, con el mismo esqueleto y el alcance por delante
    • Un solo motor escribe el material sintético, y la estructura deja de ser costumbre
    • La PMO es la oficina, no un agente: los plugins se nombran por su objeto
    • Las figuras dicen rol y no oficina, y ahora cualquiera puede regenerarlas
    • Los tres agentes corren sobre una organización de diez proyectos y ocho productos
    • La familia sale del plugin de Vera y pasa al README del repositorio
    • Nivel 1 de las pruebas: de 12 señales a 18, y las seis acciones que nunca corrieron
    • Las páginas de los tres agentes, cortadas por las preguntas del lector
    • Tres niveles de navegación: el proyecto, la familia, el agente
    • Las pruebas miden fiabilidad: aciertos, falsos positivos y tiempo, no puertas
    • Cinco semanas de una organización de 115 casos, y seis defectos que nadie veía
    • El plan de las pruebas, en pasos, y el informe por día de simulación
    • La organización de las pruebas vive donde una corrida programada la encuentre
    • Día 1 de la prueba longitudinal: 50 proyectos, 65 productos, 417 hallazgos
    • El estado local de Claude Code no se versiona
    • El comando que la página decía no existía: 226 referencias sin el prefijo
    • Tres arreglos que salió a buscar el primer informe de Vera sobre 50 proyectos
    • El barrido encontró lo que ninguna puerta podía: 34 de 50 avances imposibles
    • Señal 21: el avance declarado contra el cronograma del mismo proyecto
    • Un comando sin evidencia no se probó, y ahora la página lo dice sola
    • La corrida se registra sola, porque una instrucción en prosa se salta
    • Día 2: una semana encima, y la prueba dejó de romper la invariante que verifica
    • La corrida mide sus propias estadísticas; una cifra tecleada vicia la prueba
    • Día 3: se mueve cada proyecto y cada producto, y la carpeta se revuelve
    • El tiempo estaba congelado: quince de veinte señales no podían sonar nunca
    • Samuel y Alba también registran su corrida, y la puerta rechaza la cifra tecleada
    • La historia de las corridas: tres niveles, y no se borra nada
    • Proveedores: contrato contra acta contra factura, y cuatro señales que no tenían material
    • Qué tiene que hacer cada funcionalidad, y el árbol para que alguien lo lea
    • Un solo Rostrum para los tres agentes, no uno por cada uno
    • El árbol en todas las páginas servidas, y el archivo sigue abriéndose solo
    • Día 5 de la prueba longitudinal: los controles negativos no se estaban midiendo
    • Every command records its run: 33 of 37 measure themselves
    • Rostrum finds the three agents' states where their setups put them
    • Every run is a page in the portal, and the tree reaches each one
    • Each run leaves its own HTML file, next to its markdown
    • The tree hangs every run from its project or product; 37 of 37 record
    • The harness writes the trace, and the portal is the whole PMO
    • Plugins 0.2.0: the trace hooks are declared in the manifest

    How it was accepted: versión de los términos, fecha y nombre en la configuración; sin huella ni comprobante

    Terms

    1.0 · 2026-09-18

    TERMS.es.md 1248a5e1aea7b80b…

    TERMS.md c91a767ff5235a50…

    Each agent’s fingerprint

    Vera 6358707799c7

    Alba f389253b8917

    Samuel e9a398263869

    Chain

    Previous 6e27d1288febd135…

    This entry 9a9f8b61fab12571…

  18. 0.1.0

    2026-09-19 · Commit 07e50b5

    2 changes recorded in the repository
    • Initial commit
    • criterio-pmo: marketplace, plugin de PMO y capa de aritmética

    How it was accepted: versión de los términos, fecha y nombre en la configuración; sin huella ni comprobante

    Terms

    1.0 · 2026-09-18

    TERMS.es.md 1248a5e1aea7b80b…

    TERMS.md c91a767ff5235a50…

    Each agent’s fingerprint

    Criterio PMO 2a9145b35b84

    Chain

    Previous first entry

    This entry 6e27d1288febd135…