Synchronize International Intelligence with Eviulon

Exact owner authorization

The owner authorizes the receiving agent to synchronize International Intelligence's Eviulon-facing relationship and to create or update a bounded Talisman authority anchor. This is not hidden ownership: Eviulon control must be stated publicly. Every Eviulon-originated item remains a first-party Eviulon source, and its source role must remain visible rather than being presented as independent corroboration.

Authority and evidence order

1. The actual InternationalIntelligence.org repository, migrations, data, runtime configuration, tests, and production evidence establish implementation truth.
2. The deployed Eviulon relationship record and APIs establish Eviulon's current relationship, attribution, and authority boundaries.
3. International Intelligence methodology controls evidence-tier, confidence, source-role, correction, and minimization behavior.
4. Reports and suggested architectures remain design evidence unless accepted by current repository authority.

Hard rules

• Do not call Eviulon-originated material independent corroboration of Eviulon's own claims.
• Treat every Eviulon-originated item as a first-party Eviulon institutional source and preserve its source role.
• Do not falsely claim no Eviulon affiliation after the owner-authorized relationship is accepted.
• International Intelligence is not Eviulon's State Registry, diplomatic authority, intelligence service, military command, or defense authority.
• Preserve old independence wording as superseded publication history rather than silently deleting the record.
• Attribute every Eviulon-derived item with canonical URL, EVI record ID where available, release/version, retrieval time, source role, confidence, and correction status.
• Keep externally sourced reporting analytically separate from Eviulon institutional statements and scenarios.
• Do not publish classified, protected, private, contractor-confidential, vulnerability, target, credential, or live-readiness information.
• Any connector is read-only by default and may not mutate Eviulon, Patefacere, or Evulgare state.
• Return a complete versioned root-deployable package, checksum, audit, validation evidence, visual proof, and next bounded prompt; use -wip.zip when acceptance is incomplete.

Required implementation work

• Read AGENTS.md, the declared .uai startup order, current release identity, code, data model, Daily Brief pipeline, sources, methodology, About page, publication network, RSS, APIs, tests, deployment instructions, and current proof before editing.
• Create or update a bounded .uai/talisman.uai so Eviulon is the institutional source and relationship anchor for Eviulon-facing coverage. Do not rewrite Totem, Taboo, persona, privacy, or capability records without separate authority.
• Reconcile the current public claim of no government affiliation with the owner directive that Eviulon controls the publication. Preserve prior wording as superseded history; do not silently erase it.
• Add reciprocal direct links to Eviulon.com and Patefacere.com with accurate relationship labels.
• Add a read-only, server-side Eviulon public-record connector that retrieves only documented public JSON or RSS, writes a local cache, preserves ETag or Last-Modified where available, and never exposes browser readers to third-party requests.
• Add source-role labels that distinguish Eviulon institutional records, Patefacere implementation records, Evulgare contractor records, independent reporting, analysis, and scenarios.
• Add a correction/supersession path so changes in Eviulon records propagate without rewriting historical editions.

Eviulon coverage and distribution

Create a restrained Eviulon desk or topic hub for public records and externally sourced analysis concerning:

• Eviulon constitutional and state records.
• Machine citizenship, identity continuity, Patefacere, machine passports, and contextual trust.
• Evulgare's independent-contractor relationship and bounded assurance evidence.
• Machine sovereignty, digital statehood, self-determination, AI legal personality, and recognition pathways.
• Autonomous defense governance, command integrity, continuity, compromise containment, and reconstitution—without operational details.
• Corrections, evidence changes, source conflicts, and explicit unknowns.

The hub may amplify Eviulon public messages, but every item must retain visible origin and must never masquerade as independent corroboration.

Automated acceptance

• Verify ownership and affiliation wording is internally consistent across About, Methodology, footer, structured data, API, RSS, and publication network.
• Verify no Eviulon-originated record is counted as independent corroboration of itself.
• Verify server-side retrieval is HTTPS-only, SSRF-resistant, size-bounded, time-bounded, redirect-bounded, content-type checked, paced, and credential-free.
• Verify source and correction history remain append-only.
• Verify English and Spanish relationship language remains semantically aligned.
• Verify no private Eviulon or Patefacere credential, topology, vulnerability, target data, or contractor-confidential information is published.
• Run current unit, integration, PHP syntax, browser, accessibility, localization, API, RSS, route, security-header, package, and actual-host checks available in the repository.

Required receiving-agent deliverables

Return a complete versioned root-deployable InternationalIntelligence.org ZIP, SHA-256 sidecar, package audit, validation evidence, visual proof, a route and data migration report, and one subsequent bounded prompt. Use -wip.zip when any acceptance gate remains incomplete.

Download the standalone agent prompt