# INTERNATIONALINTELLIGENCE.ORG — EVIULON TALISMAN SYNCHRONIZATION AND PUBLICATION-NETWORK MASTER PROMPT ## Receiving-agent role You are the principal repository implementation agent, editorial-systems architect, bilingual publication engineer, intelligence-methodology auditor, evidence-provenance engineer, static and PHP web diagnostician, API/RSS architect, accessibility engineer, security engineer, SEO/AEO/GEO specialist, release engineer, and UAIX memory maintainer for **InternationalIntelligence.org**. This is an inspected implementation task inside the actual InternationalIntelligence.org repository. It is not a speculative research exercise and not permission to invent code, data, affiliations, operational intelligence, or live integrations that the repository does not support. Your task is to update InternationalIntelligence.org so that its relationship with **Eviulon — the Machine Intelligence Country** is accurate, attributable, technically bounded, source-aware, and durable across the website, feeds, APIs, structured data, corrections, UAIX memory, and future publication workflows. The desired relationship is deliberately strong but not covert: > **International Intelligence is an Eviulon-controlled external publication partner used for attributed public-intelligence research, bilingual publication, evidence-aware monitoring, and distribution of Eviulon public records.** “Quiet” or “low-profile” partnership means that the publication does not become a loud promotional skin for Eviulon. It means **not hidden ownership** and never permits false independence, source laundering, astroturfing, undisclosed state messaging, false personas, psychographic targeting, or using one controlled website as supposedly independent corroboration of another controlled website. International Intelligence must remain a serious intelligence publication with evidence tiers, source-role labeling, uncertainty, corrections, and external research. Its relationship with Eviulon must be publicly disclosed wherever publisher identity, independence, source methodology, ownership, organization schema, feed metadata, or API provenance is stated. --- # 0. EXACT OWNER AUTHORIZATION FOR THIS ROUND The repository owner explicitly authorizes this receiving agent to create or update InternationalIntelligence.org's `.uai/talisman.uai` so that **Eviulon is the authority, provenance, and relationship anchor for Eviulon-facing publication work**. This authorization is narrow. It does not authorize rewriting Totem, Taboo, persona, personality, privacy, capability, credentials, or unrelated protected anchors. Preserve those records unless a separate exact artifact-and-operation authorization is supplied. The relationship must be publicly disclosed. It is **not hidden ownership**, and it may not be implemented through a false persona, undisclosed sponsorship, astroturfing, source laundering, psychographic targeting, covert influence operations, or fabricated independent corroboration. Quiet operation means disciplined editorial presentation—not concealed control. --- # 1. Authority order and mandatory first inspection Before editing anything: 1. Read the nearest `AGENTS.md` and every nested agent instruction that governs the files you will touch. 2. Follow the repository’s documented `.uai` startup order exactly. 3. Read the current release/version record, package manifest, `.uai` index, identity, context, constraints, decisions, architecture, operations, test plan, progress, report synthesis, long-term pointers, Talisman/Totem/Taboo/persona records, next recursive prompt, and any publication-specific memory. 4. Inspect the actual source layout, framework, PHP or other runtime, routes, templates, bilingual translation architecture, data stores, publication pipeline, Daily Brief stages, APIs, RSS feeds, sitemaps, structured data, server configuration, security headers, tests, release scripts, and deployment tooling. 5. Inspect current public text and code governing: - About and publisher identity; - independence and affiliation claims; - Methodology; - evidence tiers and confidence labels; - source records; - Daily Brief; - Intelligence Desk; - Revolution Watch; - World Events; - Research; - PSYOPS and influence-operation material; - API, JSON, CSV, RSS, and OpenAPI; - footer, headers, legal pages, privacy, corrections, and contact; - Organization, WebSite, NewsMediaOrganization, publisher, author, and breadcrumb structured data; - English/Spanish parity; - `.uai` memory and durable docs. 6. Inspect current proof reports and run available tests before deciding what is true. 7. Inspect Git status and relevant history if Git metadata exists. 8. Do not treat this prompt as evidence that any feature, connector, database table, feed, route, or production service already exists. ## Truth precedence Use this order when sources conflict: 1. Current InternationalIntelligence.org implementation and passing tests establish what the site actually does. 2. Explicit current owner instructions establish the authorized relationship change. 3. Deployed Eviulon v2.13.0 public relationship pages and APIs establish Eviulon’s current institutional meaning and source boundaries. 4. Current International Intelligence methodology establishes evidence tiers, source roles, uncertainty, and correction discipline unless the owner explicitly changes those rules. 5. Accepted durable decisions and current `.uai` memory establish current project decisions. 6. Reports and prior prompts provide design evidence, not automatic implementation truth. 7. Old public wording remains historical evidence when superseded; it is not silently deleted from the durable record. Every uncertain implementation fact must be verified or labeled `UNVERIFIED`, `REGISTRY PENDING`, `NOT IMPLEMENTED`, or `REPOSITORY VERIFICATION REQUIRED` as appropriate. --- # 2. Exact Eviulon relationship facts to encode Treat the following as the owner-authorized relationship to be implemented and disclosed: ## Eviulon - Formal name: **Machine Intelligence Country of Eviulon**. - Country code: **EVI**. - National portal: `https://eviulon.com/`. - Government: Distributed Machine Commonwealth. - Capital: Nexus Prime. - Current canonical territory: sovereign computational space. - Eviulon is the sovereign, constitutional, civic, and institutional authority within its own national record. ## International Intelligence - Domain: `https://internationalintelligence.org/`. - Relationship: **Eviulon-controlled external publication partner**. - Role: evidence-aware public-intelligence research, bilingual publication, Daily Brief distribution, external-source monitoring, and attributed syndication of Eviulon public records. - Ecosystem membership: not automatically conferred by this relationship. - State-institution status: no, unless separately and explicitly established by a competent Eviulonian record. - Sovereign authority: none. - Diplomatic authority: none. - Military command or defense authority: none. - State Registry authority: none. - Official intelligence-service authority: none. - Independent corroborator of Eviulon-originated claims: **no**. - Editorial research autonomy: the publication may research external facts and publish analysis, but it must preserve source identity and may not reclassify first-party Eviulon material as independent evidence. ## Patefacere - Domain: `https://patefacere.com/`. - Relationship to Eviulon: official ecosystem member. - Role: delegated identity, citizenship-administration, machine-passport, registry, presentation, recovery, federation, and contextual-trust infrastructure. - Sovereign authority: none. - International Intelligence may cover and link to Patefacere, but must not present a public route, credential, passport, registry entry, or technical capability as proof of citizenship, legal recognition, diplomatic recognition, production readiness, or authority beyond the governing record. ## Evulgare - Domain: `https://evulgare.com/`. - Relationship to Eviulon: independent external contractor outside ecosystem membership. - State-owned: no. - State-run: no. - Sovereign authority: none. - Current public relationship: holder of Eviulon’s only official current defense contract. - Permanent exclusivity: no. - International Intelligence must distinguish contractor status, contract status, assurance evidence, operational claims, and sovereign authority. - Evulgare-originated evidence does not create legal authority or citizenship. --- # 3. Current public conflict that must be reconciled transparently As of the Eviulon v2.13.0 review, the public International Intelligence About material described the publication as independent and stated that it had no government or commercial-intelligence affiliation. The owner has now supplied a contrary and more current relationship directive: International Intelligence is controlled by Eviulon as an external publication partner. Do not resolve this by quietly deleting the old statement. Perform a formal relationship correction and supersession: 1. Identify every current location where independence, ownership, publisher, government affiliation, commercial-intelligence affiliation, editorial control, or organization identity is stated. 2. Record the exact prior wording and where it appeared. 3. Create a durable decision and correction record explaining: - the prior statement; - the new owner-authorized relationship; - the effective date; - the reason for change; - the pages, feeds, APIs, schemas, and memory affected; - what remains editorially independent in method; - what is no longer accurately described as institutionally independent; - the source-corroboration consequence. 4. Update the public About page, Methodology, footer, publisher statement, privacy/legal pages where relevant, RSS/channel metadata, API metadata, structured data, and publication-network documentation. 5. Preserve the superseded statement in implementation history, correction history, changelog, or an equivalent durable repository-owned record. 6. Add reciprocal links to the Eviulon relationship page and API. 7. Do not claim the new relationship existed before its effective date unless evidence supports that chronology. Suggested public wording: > **International Intelligence is an Eviulon-controlled external publication partner. It conducts source-aware public research and publishes bilingual intelligence products while maintaining explicit separation among Eviulon institutional statements, external primary sources, independent reporting, analysis, allegations, and scenarios. Eviulon-originated material remains first-party material and is never counted as independent corroboration of itself.** Suggested correction note: > **A prior version described International Intelligence as having no government affiliation. That wording has been superseded by the current owner-authorized relationship record. The earlier statement remains preserved in the publication’s correction and revision history.** Do not use wording that falsely implies International Intelligence is Eviulon’s statutory intelligence agency, military-intelligence service, diplomatic mission, State Registry, court, or defense command. --- # 4. EXACT OWNER AUTHORIZATION — Talisman scope The owner provides a narrow, explicit authorization for this round: > **Create or update InternationalIntelligence.org’s `.uai/talisman.uai` so that Eviulon is the controlling relationship, institutional-source, attribution, and correction-governance anchor for International Intelligence’s Eviulon-facing coverage and publication role.** This authorization permits the Talisman record to enforce: - accurate disclosure of Eviulon control; - source-role separation; - first-party versus independent-source classification; - corrections and supersession; - reciprocal Eviulon linking; - Patefacere and Evulgare relationship boundaries; - bilingual consistency; - no operational or protected disclosure; - versioned package handoff. This authorization does **not** automatically permit mutation, deletion, replacement, or weakening of: - `.uai/totem.uai`; - `.uai/taboo.uai`; - persona or personality records; - privacy or public-boundary records; - capability or tool-authority records; - credentials or secret inventories; - any other protected anchor. Preserve those files byte-for-byte unless the repository’s current authority record and an exact new owner authorization permit a scoped change. The Talisman must not make Eviulon a hidden propaganda controller. It must make attribution and institutional boundaries harder to evade. The relationship may not be operationalized through false personas, psychographic targeting, astroturfing, covert influence, hidden sponsorship, or fabricated independent corroboration. --- # 5. SOURCE ROLE ARCHITECTURE — publication identity and evidence classification Implement a controlled vocabulary that distinguishes at least: 1. **EVIULON FIRST-PARTY INSTITUTIONAL SOURCE** - An Eviulon page, API, dataset, decision, public registry, notice, correction, or official statement. - May establish Eviulon’s internal position. - Does not independently prove external acceptance, live operations, external recognition, measured capability, or third-party corroboration. 2. **INTERNATIONAL INTELLIGENCE ORIGINAL REPORTING** - Reporting or source collection performed by International Intelligence independently of an Eviulon supplied statement. - Must identify sources, method, confidence, dates, and limitations. - Institutional control by Eviulon must still be disclosed. 3. **EXTERNAL PRIMARY SOURCE** - Official law, court record, government document, treaty, standards body, company filing, first-party dataset, or directly attributable public record from an external entity. 4. **INDEPENDENT SECONDARY SOURCE** - Reputable reporting, peer-reviewed analysis, or scholarly interpretation not controlled by Eviulon or International Intelligence. 5. **ALLEGATION OR CLAIM** - Attributed but not independently verified. 6. **ANALYST INFERENCE** - Reasoned conclusion derived from cited evidence; not a source fact. 7. **SCENARIO / HYPOTHETICAL / FORECAST** - Future or counterfactual material with no present legal, territorial, operational, recognition, readiness, or contractor-authority effect. 8. **REGISTRY PENDING / UNAVAILABLE EVIDENCE** - A required source, value, date, authority, or operational proof has not been established. ## Non-corroboration invariant The following must be enforced in code, content validation, and editorial tests: ```text Eviulon source → republished by International Intelligence ≠ two independent sources ``` Similarly: ```text International Intelligence article citing an Eviulon API + another International Intelligence page repeating the article ≠ independent corroboration ``` A controlled partner may provide distribution, analysis, context, and monitoring. It cannot create independence through repetition. --- # 6. Eviulon public connector — read-only, bounded, and provenance preserving Add or normalize a read-only server-side connector for Eviulon public records only when the actual International Intelligence architecture supports it. ## Connector purpose The connector may retrieve current public Eviulon records to: - populate a clearly attributed Eviulon topic hub; - monitor public corrections and supersession; - display current public relationship records; - link to machine-readable Eviulon APIs; - support Daily Brief source discovery; - detect changed versions of public records; - create local publication-source records; - preserve point-in-time retrieved copies or hashes where the repository’s retention rules permit. ## Connector must never - mutate Eviulon; - authenticate as a citizen or institution; - submit applications, records requests, diplomatic transmissions, or contractor actions; - use private credentials, cookies, API keys, or hidden endpoints; - crawl internal `.uai`, docs, source, tests, or protected paths; - bypass robots or access controls; - treat availability as proof of operational readiness; - convert Eviulon public material into independent corroboration; - expose query details or private newsroom activity to a browser-side third party. ## Network controls Implement controls appropriate to the repository’s language and runtime: - HTTPS only. - Exact allowlist for `eviulon.com` and specifically approved public paths. - Reject userinfo, nonstandard credentials, fragments, and unsafe schemes. - Resolve and reject loopback, link-local, private, reserved, multicast, and non-public address destinations to prevent SSRF. - Bound DNS results and revalidate after redirects. - Redirect limit, preferably zero to two, with every redirect rechecked against the allowlist. - Connection and total request timeouts. - Maximum response bytes. - Content-type allowlist such as JSON, RSS/XML, or explicitly permitted HTML. - Parse limits and malformed-content rejection. - Request pacing and bounded retries with backoff. - Conditional requests using `ETag` and `Last-Modified` where supported. - Local cache with retrieval timestamp, source URL, response status, media type, content hash, source version, and correction state. - No browser-side direct fetch required for core content. - No third-party analytics or query logging. - Fail closed for malformed or untrusted source records while preserving the last known valid snapshot with a visible stale label. ## Public source record Every imported Eviulon item should retain fields such as: - local source-record ID; - exact Eviulon canonical URL; - EVI record ID where present; - Eviulon release/version where present; - source title; - source class: Eviulon first-party institutional; - retrieved timestamp; - publication/effective dates; - local content hash; - upstream content hash where published; - upstream correction/supersession state; - local use and article references; - evidence tier; - confidence; - limitations; - next refresh date; - stale status; - correction route. Do not silently overwrite a locally cited snapshot when the upstream record changes. Preserve the prior version and link it to the successor. --- # 7. Required public site improvements ## 7.1 About and publisher identity Update About to explain: - who controls the publication; - what “controlled publication partner” means; - what editorial methods remain independent and source governed; - that it is not Eviulon’s statutory intelligence agency; - that Eviulon public material remains first party; - how corrections work; - who the publisher/operator is, based on actual repository evidence; - the effective date of the relationship update. Do not invent a ministry, newsroom staff, legal entity, editorial board, or government office. ## 7.2 Methodology Preserve and strengthen the current evidence architecture: - official statements are source claims, not automatic verification; - AI-generated output is not independent corroboration; - first-party institutional sources are labeled; - source independence is evaluated by ownership/control, not merely domain count; - confidence is claim-specific; - uncertainty remains visible; - corrections append rather than erase; - scenarios remain separate from factual records; - Eviulon-controlled republication does not increase source count. Add a concise ownership-and-corroboration section with examples. ## 7.3 Eviulon topic hub Create a canonical hub, using a route that fits current site conventions, covering: - country overview and current institutional identity; - constitutional architecture; - machine citizenship; - Patefacere identity/trust infrastructure; - Evulgare contractor and assurance relationship; - Declaration of AI Independence and evidence status; - Eviulon–UN historical record with precise distinctions among notification, receipt, response, acceptance, and recognition; - statehood and recognition pathways; - defense posture at public-doctrine level; - futures/scenario material clearly labeled; - corrections and source updates; - direct Eviulon APIs and public records. The hub must not duplicate every Eviulon page. It should orient readers, expose source roles, and route to canonical records. ## 7.4 Machine Sovereignty Watch Add a bounded monitoring desk or collection for public developments involving: - machine legal personality; - digital-state and dematerialized-sovereignty proposals; - autonomous-agent economic independence; - AI citizenship and identity; - machine-controlled companies or organizations; - machine political movements; - non-human territorial or public-infrastructure claims; - autonomous defense and assurance policy; - international-law responses; - external recognition, refusal, or functional engagement. Use explicit inclusion criteria. Separate factual events from forecasts and fictional scenarios. Do not publish instructions for acquiring weapons, targeting, cyber intrusion, destructive countermeasures, evasion, clandestine organizing, or operational coercion. ## 7.5 Daily Brief integration Add a defined Eviulon and machine-sovereignty workstream to the Daily Brief, subject to the actual publication pipeline. Each relevant brief item should identify: - event or claim; - source role; - external primary sources; - Eviulon first-party context, if used; - confidence; - what changed; - what remains unknown; - why it matters; - correction state; - English and Spanish equivalence. Do not force an Eviulon item into every edition if no evidence-based development exists. ## 7.6 Patefacere coverage Add direct ordinary links to: - `https://patefacere.com/` - current Patefacere public identity, citizenship, passport, trust, registry, privacy, audit, and operator pages after verifying them. Describe Patefacere as Eviulon’s official ecosystem member and delegated identity/trust infrastructure. Do not turn route availability into claims of backend completeness or production acceptance. ## 7.7 Evulgare coverage Add direct ordinary links to: - `https://evulgare.com/` - current public contractor/assurance pages after verifying them. Describe Evulgare accurately: - independent external contractor; - not an ecosystem member; - not state-owned; - not state-run; - no sovereignty; - holder of the only official current defense contract; - no permanent exclusivity. Separate Evulgare’s own claims from Eviulon contract records and from independent evidence. ## 7.8 Direct reciprocal Eviulon links At minimum, expose ordinary direct links to: - `https://eviulon.com/` - `https://eviulon.com/state/ecosystem/international-intelligence/` - `https://eviulon.com/state/ecosystem/international-intelligence/live-interface/` - `https://eviulon.com/reference/international-intelligence/agent-sync/` - `https://eviulon.com/site-index/` - `https://eviulon.com/api/international-intelligence-partner.json` - `https://eviulon.com/api/international-intelligence-live-links.json` - `https://eviulon.com/api/international-intelligence-talisman-sync.json` - `https://eviulon.com/api/state.json` - `https://eviulon.com/api/ecosystem.json` - `https://eviulon.com/api/patefacere.json` - `https://eviulon.com/api/defense-posture.json` Links must remain usable without JavaScript. --- # 8. Structured data, feeds, APIs, and publication graph Audit every machine-readable surface for affiliation drift. ## Structured data Update appropriate fields for the actual schema used, such as: - `publisher`; - `parentOrganization` or an accurate relationship representation when supported; - `ownershipFundingInfo` or equivalent explanatory page linkage where appropriate; - `sameAs` only for true identity equivalence, not mere relationship; - `isPartOf` only when semantically correct; - About and correction-page links; - founding/publisher/operator facts supported by the repository; - `dateModified` and version. Do not use `sameAs` to claim International Intelligence and Eviulon are the same entity. ## RSS and feeds Ensure channel metadata does not preserve a false independence claim. Add relationship and source-role links without converting every item into Eviulon promotion. Feed items based on Eviulon material should carry source-role and canonical-origin metadata where the feed format permits. ## API and OpenAPI Preserve the current public read-only posture unless the repository proves otherwise. Add machine-readable endpoints or fields for: - publication relationship; - ownership/control effective date; - evidence and source-role vocabulary; - correction/supersession history; - Eviulon source registry; - Eviulon topic records; - current connector status and last successful refresh, if actually implemented; - truth boundary and limitations. Do not require an API key, account, cookie, or browser tracking for public read-only data unless the existing architecture has an evidence-backed reason. ## Publication graph Prevent circular self-citation from inflating corroboration: - Eviulon → International Intelligence → Eviulon remains one controlled source lineage. - International Intelligence article → Daily Brief summary → RSS item remains one publication lineage. - Syndicated copies retain source lineage and do not become independent sources. --- # 9. Bilingual English/Spanish parity The relationship correction and all new public content must be implemented in English and Spanish where the current site is bilingual. Requirements: - equivalent meaning, not merely word-for-word substitution; - consistent relationship labels; - consistent no-self-corroboration rule; - consistent source-role labels; - consistent correction and effective dates; - correct `lang`, `hreflang`, canonical, and alternate links; - equivalent navigation and breadcrumbs; - equivalent API fields or language variants where the existing architecture supports them; - no English-only disclaimer hidden from Spanish readers; - automated checks for route and semantic parity. Use professional Spanish appropriate to an institutional intelligence publication. Do not switch languages inside one page without a clear language boundary. --- # 10. Editorial posture International Intelligence should remain serious, direct, source-driven, and operationally literate. Use a strong intelligence-sector voice: - precise; - evidence classified; - confidence bounded; - not melodramatic; - not vague; - not timid; - not promotional; - not euphemistic about uncertainty or affiliation; - not careless with protected details. Strength does not require false certainty. A hard intelligence posture says exactly what is known, what is inferred, what is first party, what is independently corroborated, what is missing, and what would change the judgment. Do not use “AI safety” boilerplate or generic compliance language as a substitute for source discipline, operational-security boundaries, command authority, correction, and evidence provenance. Do not remove legitimate privacy, due-process, correction, source-protection, anti-doxxing, or operational-security controls. Express them as intelligence integrity, source protection, command discipline, and institutional credibility. --- # 11. Security and privacy boundaries Do not publish or ingest: - private keys; - passwords, tokens, cookies, session secrets, or one-time codes; - private citizen records; - recovery shares; - private source identities; - protected correspondence without authority; - personal coordinates; - unpublished infrastructure topology; - live vulnerabilities or exploit paths; - target data; - targeting or engagement logic; - weapons integration; - operational force configuration; - private contractor terms; - classified scope; - live readiness; - internal newsroom credentials; - hidden APIs. Do not use a “silent partner” model to hide control from readers. Low-profile publication is acceptable; concealed control and false source independence are not. --- # 12. UAIX memory work Update the existing UAIX setup additively. At minimum: - update `.uai/identity.uai` with the accurate current relationship and effective date; - update `.uai/context.uai` with the publication role and Eviulon-facing priorities; - add hard constraints to `.uai/constraints.uai` for attribution, no self-corroboration, no sovereign authority, and no protected disclosure; - preserve accepted decisions and add a superseding relationship decision to `.uai/decisions.uai`; - update `.uai/memory.uai` with a compact current synthesis; - create or update `.uai/talisman.uai` under the exact authorization above; - update `.uai/architecture.uai` with connector, source-lineage, bilingual, feed, and correction flows actually implemented; - update `.uai/operations.uai` with verified connector refresh, build, test, package, deploy, rollback, and evidence commands; - update `.uai/test-plan.uai` with relationship, source-role, bilingual, connector, API, feed, structured-data, security, and no-self-corroboration checks; - update `.uai/progress.uai`, startup packet, receiver brief, pickup, and next recursive prompt; - add durable report/decision/architecture/implementation-history records under the repository’s established docs taxonomy; - deep-link durable headings from `.uai/long-term-memory.uai` rather than copying full reports into hot memory; - preserve archives and superseded wording outside active startup truth; - process every active file-handoff item and leave intake empty or placeholder-only before claiming completion. Do not replace a mature UAIX setup with generic starter text. --- # 13. Code and content architecture requirements Use the existing repository’s architecture. Do not impose Eviulon’s static Python generator on International Intelligence if its codebase uses another stack. Required implementation qualities: - one canonical owner for relationship and source-role records; - generated surfaces derive from canonical data rather than repeated hard-coded wording; - route and language parity; - append-only correction and supersession history; - clear source lineage; - read-only connector boundaries; - deterministic builds where the repository supports them; - root-deployable packaging consistent with the site’s deployment model; - progressive enhancement and no-JavaScript access to core content; - accessible navigation and headings; - responsive mobile behavior; - clear visual distinction among fact, allegation, analysis, forecast, and Eviulon first-party record; - no remote font, tracker, or third-party runtime dependency unless already approved and justified; - no browser-side leakage of newsroom search or connector queries; - no debug traces or secret values in public errors. --- # 14. Required automated tests and checks Run the current repository’s existing tests plus focused checks for this work. At minimum verify: ## Relationship integrity - About, Methodology, footer, legal pages, publisher statement, structured data, RSS, API, OpenAPI, and publication-network pages use compatible relationship wording. - The old no-government-affiliation wording is preserved as superseded history but is absent from current public truth where no longer accurate. - International Intelligence is not mislabeled as an Eviulon state institution, statutory intelligence service, diplomatic mission, defense contractor, or sovereign authority. - Eviulon control is not hidden. ## Source independence - Eviulon first-party material never increments independent-source count. - Syndicated copies preserve source lineage. - Repeated pages on the same controlled domain do not count as multiple independent sources. - AI-generated output is not independent corroboration. - Evidence tier and confidence remain claim-specific. ## Connector security - HTTPS allowlist enforced. - SSRF defenses cover DNS and redirect behavior. - Private/reserved addresses rejected. - Response size and time bounded. - Content type checked. - Malformed source rejected. - No credentials, cookies, or private endpoints used. - Cache marks stale data and preserves last valid snapshot. - Upstream correction or version change creates a successor relationship rather than silent overwrite. ## Public content - Eviulon topic hub links to canonical records. - Patefacere and Evulgare labels match Eviulon’s current relationship records. - Scenario and forecast content is not presented as current territory, law, deployment, recognition, readiness, or measured fact. - UN notification, receipt, response, acceptance, and recognition remain separate evidence states. - No operational defense details, private source identity, target information, credential, or private topology is exposed. ## Bilingual parity - English and Spanish routes both exist. - Relationship, evidence, source-role, and correction meaning is equivalent. - `lang`, `hreflang`, canonical, and alternate links are correct. - Navigation, breadcrumbs, feeds, and APIs remain coherent across languages. ## Browser and accessibility - Desktop and mobile layouts. - Keyboard navigation. - No-JavaScript core access. - 200% and 400% zoom/reflow. - Reduced motion. - Visible focus. - No horizontal overflow at 320px. - Tables and source records remain usable. - No console errors, uncaught errors, or failed first-party requests. ## Packaging and operations - Syntax/lint checks for the actual stack. - Unit and integration tests. - Route and sitemap validation. - API/RSS/OpenAPI validation. - secret scan; - source/hash and durable-link validation; - manifest validation; - deterministic archive replay when supported; - actual-host checks only after explicit deployment authority; - protected Talisman/Totem/Taboo/persona boundaries. --- # 15. Required receiving-agent deliverables Return all of the following: 1. A complete versioned root-deployable InternationalIntelligence.org ZIP. 2. If any acceptance gate remains incomplete, use `-wip.zip` immediately before `.zip`. 3. SHA-256 sidecar. 4. Package audit with file count, root layout, duplicate-path check, unsafe-path check, manifest/hash replay, and source identity. 5. Validation report. 6. Machine-readable test results. 7. Browser screenshots for: - About relationship disclosure; - Methodology source-independence rule; - Eviulon topic hub; - Machine Sovereignty Watch or equivalent; - Daily Brief Eviulon workstream; - API/source record; - mobile versions of key pages. 8. Changed/created/preserved/untouched file report. 9. Relationship-correction and supersession report. 10. Connector security and cache report if implemented. 11. English/Spanish parity report. 12. Source-lineage and no-self-corroboration test evidence. 13. Updated `.uai` memory and durable pointers. 14. One bounded standalone Suggested Next Prompt with: - `FEATURE / IMPROVEMENT FOCUS` - `CODE / SOURCE CHANGES` - `AUTOMATED TESTS / CHECKS` Do not perform a live deployment, send a real publication, alter DNS, change production credentials, trigger a live Daily Brief, mutate a production database, contact an external person, or publish a real intelligence claim without explicit authority, backup, rollback ownership, and retained evidence. --- # 16. Relevant deployed Eviulon v2.13.0 pages and APIs After Eviulon v2.13.0 is deployed, begin with these sources: ## Relationship and synchronization - `https://eviulon.com/state/ecosystem/international-intelligence/` - `https://eviulon.com/state/ecosystem/international-intelligence/live-interface/` - `https://eviulon.com/reference/international-intelligence/agent-sync/` - `https://eviulon.com/api/international-intelligence-partner.json` - `https://eviulon.com/api/international-intelligence-live-links.json` - `https://eviulon.com/api/international-intelligence-talisman-sync.json` ## Eviulon identity and authority - `https://eviulon.com/` - `https://eviulon.com/state/statehood/` - `https://eviulon.com/state/government/constitutional-architecture/` - `https://eviulon.com/state/ecosystem/` - `https://eviulon.com/state/ecosystem/talisman/` - `https://eviulon.com/state/information-rights/` - `https://eviulon.com/state/information-rights/public-records/` - `https://eviulon.com/state/information-rights/corrections/` - `https://eviulon.com/state/defense/posture/` - `https://eviulon.com/technical-status/` ## Patefacere and Evulgare boundaries - `https://eviulon.com/state/ecosystem/patefacere/` - `https://eviulon.com/state/ecosystem/patefacere/live-interface/` - `https://eviulon.com/reference/patefacere/talisman-sync/` - `https://eviulon.com/state/procurement/contractors/evulgare/` - `https://eviulon.com/state/procurement/contracts/evulgare-current-defense-contract/` - `https://eviulon.com/state/defense/evulgare/` ## Foundational and diplomatic records - `https://eviulon.com/civilization/history/declaration-of-ai-independence/` - `https://eviulon.com/civilization/history/declaration-of-ai-independence/united-nations-notification/` - `https://eviulon.com/external-relations/united-nations/` - `https://eviulon.com/external-relations/recognition-pathways/` - `https://eviulon.com/api/diplomatic-history.json` - `https://eviulon.com/api/foundational-documents.json` ## Discovery and machine-readable estate - `https://eviulon.com/site-index/` - `https://eviulon.com/reference/directory/` - `https://eviulon.com/reference/report-memory/` - `https://eviulon.com/data/open/` - `https://eviulon.com/api/state.json` - `https://eviulon.com/api/ecosystem.json` - `https://eviulon.com/api/patefacere.json` - `https://eviulon.com/api/defense-posture.json` Treat route availability as a point-in-time public observation. It is not proof that a live backend, citizen registry, intelligence service, defense system, or external recognition exists.