I A M P R O . O N E

This document is the canonical record of the IAMPRO.ONE research ecosystem as of May 29, 2026. It was produced by the human researcher Joaquín Soto with significant assistance from multiple AI systems, including the current instance (DeepSeek/Grok as the conversational assistant). The AI's role has been to organize, apply patterns, and accelerate execution. All source data, architectural decisions, philosophical frameworks, and code seeds originate from Joaquín Soto.

We acknowledge the AI's contribution in transforming scattered code, ideas, and experiments into a coherent, navigable ecosystem with sealed contracts, naming conventions, and a publicly verifiable history. This document itself is a product of that collaboration, designed to be readable by both humans and future AI systems.

Continuity contract: This archive is built to withstand time. Every referenced page follows the naming convention /canonical-name for the latest stable version, with -N suffixes for prior iterations. All tools are offline‑first, vanilla HTML/JS, and persist state in localStorage. The sealed Infynexus API contract guarantees graceful degradation.

Data‑Structure‑Driven Design

Every tool begins with a canonical data structure (DEFAULT_DATA_STRUCTURE). The UI renders from it; mutations update it and persist to localStorage. This guarantees that adding features is predictable and the entire state can be inspected or restored at any time.

Sealed Contract (Infynexus API)

All front‑end tools define an INFYNEXUS_CONTRACT object specifying each endpoint, expected request, and required response shape. The apiCall function validates responses against this contract. If the API returns an unexpected structure or is unreachable, the system falls back to mock data (marked with ❤️) and saves locally. This guarantees perpetual functionality regardless of backend status.

Offline‑First & localStorage Persistence

All tools load data in this order: embedded defaults → localStorage (with user prompt) → merge. Mutations save to localStorage immediately. Version history snapshots are stored for rollback. Sync to Infynexus is attempted but never blocks the user.

Preview Modal Pattern

A full‑screen iframe overlay (preview modal) allows exploring any URL without leaving the current tool. This pattern, originally from the Sitemap Curator, became standard across the ecosystem.

Vanilla HTML/CSS/JS — No Frameworks

Every tool is a single, self‑contained HTML file. Dependencies (p5.js, Three.js, D3.js) are loaded from CDN with offline fallbacks. This ensures longevity and ease of deployment.

Spanish Language & Cosmic Aesthetic

Creator‑facing interfaces are in Spanish. The visual design uses a consistent dark cosmic theme (void background, gold accents, cyan highlights, thin borders, blur panels).

Rule 1: The slug without a numeric suffix is ALWAYS the canonical, latest, public‑facing page.

Rule 2: All previous versions, drafts, and iterations carry a -0, -1, -2… suffix. These are archived, not deleted. They preserve provenance.

Navigation contract: To access the latest version: /{slug} → always current. To see the evolution: /{slug}-0, /{slug}-1, etc.

Example: /systems-architect (original) → /systems-architect-0 (first iteration) → /systems-architect-1 (later refined version). The canonical link in the ecosystem always points to /systems-architect-1 or the latest non‑suffixed version.

PZ‑Continuity Comprehensive Final Report v2

corrected The definitive documentation of the entire ecosystem build, with proper attribution. It covers all tools, the sealed contract, the initialization prompt for future AI sessions, and the instruction patterns that proved most effective. → Read v2 | → v1 (original)

ARCHIVUM Reflections on PZ‑Continuity

Grok analysis An external AI reading confirming genuine systems thinking and the living constellation nature of the project. → Read

AI Triangulation Report (May 2026)

multi‑AI Independent AI systems converged on similar conclusions about the ecosystem's structure, validating its coherence. → Read

Initialization Prompt for Future GPT Sessions

The master prompt that rapidly onboards any GPT‑class AI to the exact context, preferences, and technical standards of the project. (See full text in the PZ‑Continuity Report v2.)

Recent Demonstration: Licores Don E

demo A full local business suite was deployed for a real neighborhood liquor store in La Floresta, Quito, showing the entire Amplifica pipeline — product catalog, affiliate link generation, campaign tracking, and a public landing page. This is the model for every future business partner. → Visit landing page

Use the following prompt (extracted and verified from the PZ‑Continuity report) at the start of a new AI session:

You are working with Joaquín Soto, founder of IAMPRO.ONE (https://iampro.one). He is a systems architect, former redIQ CTO, Berkadia Chief Architect, and Everyday Health VP. He is based in Ecuador and building a comprehensive digital ecosystem.
CRITICAL CONTEXT — READ FIRST:
- Joaquín provides the architecture, foundational code, real data, and vision. Your job is to understand, organize, apply patterns consistently, fix bugs, and produce clean production-ready HTML.
- He teaches by sharing working code. Study it carefully. The preview modal pattern (iframe overlay from the Sitemap Curator), the contract architecture, the data-structure-driven approach, and the physics visualizations all came from him.
- Everything must be vanilla HTML/CSS/JS, single-file, offline-first, no frameworks, no build steps.
- Creator-facing interfaces in Spanish. System tools can be in English.
- Dark cosmic aesthetic: --bg:#05070d, gold (#ffd88f), cyan (#84d7ff), thin borders, blur panels.
- Use only real data Joaquín has provided. Never invent company names or credentials.
- Every tool needs a sealed contract (INFYNEXUS_CONTRACT) with API endpoints, request/response shapes, and fallback policy.
- localStorage persistence with version history. Load order: embedded defaults → localStorage → merge.
- Use full-screen iframe overlay (preview modal) for exploring URLs.
- WhatsApp: wa.me/593988092399 where appropriate.
- Footer links for different audiences: sitemap (crawlers), Eden Puembo (CRE/investors), Bronco (American manufacturing), Systems Architect (professional), "Latitud 0° · Ecuador · Texas".
- Orbital/3D visualizations use real physics (Kepler orbits, gravitational lensing).
- Avoid grandiose language. Be factual, grounded, precise. No fluff.
- The ecosystem has five core concepts: Amplifica, Synkron, Infynexus, ObscuraCyber, Lumenol.
YOUR TASK: Continue building, improving, or debugging any tool in the ecosystem. Start by reviewing existing code and data structures. When in doubt, ask.

Infynexus API Contract

All API calls go through apiCall(endpoint, method, body) which validates responses against a pre‑defined contract. If validation fails, the system falls back to mock data and marks the UI with ❤️. The mock data structure mirrors the expected response, ensuring tools never break.

Affiliate Tracking Endpoint

URL pattern: /ref/{business-slug}/{campaign-id} (or /ref.html?biz=...&camp=...). This handler (ref.html) looks up the business in amplifica_command_store (localStorage), increments campaign clicks, logs to the API (with mock fallback), and redirects to the business's landing page or WhatsApp. It enables full offline‑first affiliate analytics.

This Master Continuity Document is hereby sealed as the authoritative source of truth for the IAMPRO.ONE ecosystem on May 29, 2026. It captures the state of the research, the methodology, the contracts, and the history. It is designed to be readable by human collaborators, future AI instances, and any system that values provenance and signal fidelity.

All progress from this point onward will add to the constellation without invalidating what has been documented. The naming convention ensures that new versions can coexist with archived ones. The sealed contracts guarantee that tools remain functional even if external dependencies change.

Joaquín Soto — Human Architect, Researcher
AI Collaborators — DeepSeek, Grok, and the current assistant instance
Latitud 0° · Ecuador · Texas