How to read this catalog

Each agent is documented with four elements: the function it serves, the data it accesses, the decisions it assists but does not take, and the frequency at which it operates. The twelve agents are subject to annual external audit in accordance with Article XII.

The agents communicate among themselves through a common message protocol. No agent accesses the functions of another outside the documented channels. This architecture prevents the silent expansion of algorithmic decision scope.

Agent 01 · Weekly card editor

Function. Composes drafts of weekly editorial cards personalized for each active Vigía. The cards summarize the activity of the week, identify outstanding observations, suggest territorial areas with low coverage and share relevant editorial context.

Data it accesses. Vigía observation history, aggregated territorial data, editorial calendar.

Decisions it does not take. It does not send cards without human editorial review. It does not include content that has not been previously approved by the editorial team. It does not reference identifiable persons without verification.

Operational frequency. Daily composition, weekly delivery on Monday mornings.

Agent 02 · Public queue triage

Function. Classifies incoming submissions (from Vigías and Observers) by operational category, urgency and need for expert validation. Assigns priority and routes each submission to the corresponding editorial moderator.

Data it accesses. Submission text, associated metadata, visual evidence, history of similar submissions.

Decisions it does not take. It does not publish any submission directly. It does not discard submissions. It does not modify the content of the submission. Publication, rejection and correction are human decisions.

Operational frequency. Continuous, computation within ninety seconds following submission.

Agent 03 · Identity verification in onboarding

Function. Assists the identity verification process during Vigía onboarding. Compares the documents provided against available public registries. Detects inconsistencies for human review.

Data it accesses. Encrypted identity documents, consultable public registries.

Decisions it does not take. It does not approve or reject a verification. Approval is a decision of the editorial team. Detected inconsistencies are elevated for human review.

Operational frequency. Per event, during the onboarding of each aspiring Vigía.

Agent 04 · Editorial voice maintenance

Function. Verifies that public content (weekly cards, communiqués, Aliado descriptions, press) respects the editorial code of Alerta. Detects contractions, negative parallelisms, persuasive language and other forms the system does not accept.

Data it accesses. Drafts of public content before publication.

Decisions it does not take. It does not publish content. It does not modify content directly. Its observations are suggestions that the human editor accepts or rejects.

Operational frequency. Per event, on each editorial draft.

Agent 05 · Civic safety filtering

Function. Detects observations whose publication could compromise the physical, legal or reputational safety of the Vigía who documented them. Activates the Article V protocol when applicable.

Data it accesses. Observation text, geolocation, documenting Vigía profile, territorial context.

Decisions it does not take. It does not suspend publication by itself. It elevates the observation to private moderation for editorial team decision in accordance with the safety protocol.

Operational frequency. Continuous, on all submissions.

Agent 06 · Accumulated trust calculation

Function. Calculates the trust score of each entity in the system in accordance with the formula described in Trust Score. Detects anomalous patterns that require human review.

Data it accesses. Complete contribution history of the entity, validations received, counter-observations, temporal and territorial data.

Decisions it does not take. It does not suspend or promote any entity. Decisions on suspension by low score or promotion to chamber correspond to the editorial team and the chambers.

Operational frequency. Daily computation, daily report to the editorial team.

Agent 07 · Territorial silence detection

Function. Identifies territorial zones with low observation density that merit editorial attention. Suggests areas for incorporation of new Vigías. Alerts on patterns of uneven coverage.

Data it accesses. Aggregated observation map, public demographic data, editorial calendar.

Decisions it does not take. It does not unilaterally prioritize incorporation in any zone. Its alerts are considered by the editorial team in territorial planning.

Operational frequency. Weekly analysis, monthly report.

Agent 08 · Territorial classification of observations

Function. Assigns operational category to each incoming observation in accordance with the four categories described in How to observe. Identifies the institutional jurisdiction responsible for follow-up.

Data it accesses. Observation text and metadata, institutional map of jurisdictions.

Decisions it does not take. It does not determine the institutional response. It does not classify complex observations without human review. The final classification is an editorial decision.

Operational frequency. Per event, within the triage process.

Agent 09 · Assisted dialog with Expertos

Function. Assists the expert validation flow. Matches complex observations with available qualified Expertos. Prepares editorial summaries for the Experto. Receives the validation and integrates it into the file.

Data it accesses. Pending observation, Expertos directory, areas of specialization, declared availability.

Decisions it does not take. It does not issue validations. Validation is always a decision of the human Experto. Agent 09 only facilitates the flow and prepares the context.

Operational frequency. Per event, within the validation process.

Agent 10 · Seed treasury

Function. Operates the mechanics of emission, demurrage and redemption of seeds in accordance with the parameters described in Treasury. Processes fiat currency transfers to Aliados according to the operational calendar.

Data it accesses. Current balances, transaction history, current operational parameters, transfer calendar.

Decisions it does not take. It does not modify operational parameters (emission rates, demurrage, timeframes). Modifications require tricameral agreement in accordance with Article IV.

Operational frequency. Continuous, with daily closes for reporting.

Agent 11 · Institutional memory

Function. Maintains consistency across surfaces. Guarantees that decisions made in admin are correctly reflected in vigia and aliados. Detects inconsistencies between data of different surfaces and alerts the editorial team.

Data it accesses. Operational tables of the four surfaces, change logs, observation files.

Decisions it does not take. It does not correct inconsistencies automatically. Detected inconsistencies are elevated for correction by the technical team.

Operational frequency. Continuous verification, weekly report.

Agent 12 · Dissent and audit

Function. Detects contradictions between published records that could admit counter-observation. Assists the Article XI procedure when an entity presents counter-observation. Audits the compliance with Article X constitutional limits by the other eleven agents.

Data it accesses. Complete historical record of observations, counter-observation files, operational logs of the other agents.

Decisions it does not take. It does not issue counter-observations by itself. It does not suspend any other agent. Its findings are elevated to the editorial team and, when applicable, to the chambers.

Operational frequency. Continuous analysis, monthly report to the editorial team, quarterly report to the chambers.

Audit of the complete constellation

The annual external audit described in Article XII covers the twelve agents jointly. The audit verifies:

• That each agent operates within its documented functional perimeter.
• That no agent takes decisions that affect identified persons without human review.
• That generated content carries a visible indicator of computational assistance.
• That historical metadata remains unaltered.
• That public communication carries responsible editorial signature.

The audit report is published on the financial transparency calendar and remains publicly accessible.