EI-7.4 — paco.io Technology Publication Architecture

Status: COMPLETE Date: 2026-08-08

Decision

paco.io is the technology publication in the Francisco Rodríguez web ecosystem.

Its role includes:

general technology news and curated reporting;
PTIR;
technology commentary;
projects, experiments, and tools;
selected technical notes and digital-garden material.

The existing Antigravity-built retro terminal / Obsidian-vault interface is a preservation constraint and a design asset. EI-7.4 extends the editorial architecture inside that system rather than replacing it with a conventional blog design.

Preservation baseline

The following existing behaviors are intentionally preserved:

retro terminal/CRT visual identity;
Phosphor Green, Classic Amber, Neon Cyberpunk, and Print Paper themes;
CRT preference control;
Vault Explorer and search;
Obsidian-style Markdown publishing;
backlinks and vault navigation;
keyboard/terminal interaction patterns;
existing vault/ and wtf/ content;
GitHub Pages/Jekyll deployment model.

Publication model

Technology News

Jekyll posts become the chronological technology-publication stream. New posts default to:

content_type: technology-news
publication: paco.io

Curated reporting should include source metadata where practical, such as:

source_name: Example Publication
source_url: https://example.com/original-story
editorial_mode: curated

Original technology commentary can instead use:

content_type: commentary
editorial_mode: original

Outside reporting should be linked and summarized rather than reproduced.

PTIR

/ptir/ is established as PTIR’s permanent destination architecture.

PTIR is explicitly an AI-assisted operated publication, not a Francisco-authored personal Blog. PTIR content should use:

publication: PTIR
content_type: operated-publication
ai_assisted: true

EI-7.4 does not migrate or delete historical PTIR editions. That work belongs to EI-7.5.

Vault / projects

The Vault remains a first-class technical-notes and project environment. It complements the news/publication stream rather than serving as paco.io’s sole identity.

Ecosystem boundaries

paco.org: personal publication, Blog, entertainment, social/check-in material, career identity, and historical archive.
idtprof.net: technology education publication, lessons/course resources, education news, and news relevant to teaching subjects.
paco.io: technology news, PTIR, technology commentary, projects/tools, and technical digital-garden material.
firg.xyz / idtprof/portal: operational teaching dashboard; read-only unless explicitly authorized.

EI-7.5 destination contract

PTIR migration must account for:

all existing paco.org PTIR edition URLs;
/ptir/ landing-page continuity;
canonical destinations and redirects;
RSS/feed subscribers;
publishing automation targets;
historical publication dates and edition identity;
cross-links among old and new reports;
explicit AI-assisted/operated authorship metadata;
search/indexing continuity;
rollback safety until the new paco.io archive is verified.

The paco.org privacy exclusion remains absolute: historical DELETE material, including protected material involving Ben and/or Sophie and associated excluded media, must never enter PTIR migration or production sources.

EI-7.5 recommendation

Proceed with a staged PTIR extraction:

inventory the existing paco.org PTIR corpus and current automation/feed behavior;
implement the paco.io PTIR post/archive/feed model;
copy and verify historical PTIR editions without deleting paco.org originals;
update publishing automation to paco.io;
establish canonical/redirect behavior;
verify links, feeds, dates, and indexing;
only then retire duplicate serving behavior on paco.org.

PACO.IO