EI-7.5 — PTIR Extraction & Migration Closeout

Status: COMPLETE
Date: 2026-08-08

Outcome

The Personal Technology Intelligence Report (PTIR) has moved from paco.org to paco.io as an AI-assisted operated technology publication.

Historical archive

23 production editions were migrated, spanning July 28 through August 8, 2026.
Original publication dates, titles, bodies, and explicit permalink paths were preserved.
The archive recognizes historical series: PTIR metadata and the one legacy categories: PTIR edition without rewriting the historical body content.
/ptir/ is the canonical paco.io publication index.
/ptir/feed.xml is the PTIR-specific Atom feed and contains all 23 historical editions at migration closeout.
General Technology News discovery on the paco.io homepage excludes PTIR, keeping the operated publication distinct from the general news stream.

Source continuity

paco.org retains the historical source in Git history but no longer serves PTIR as a local publication. Its 23 historical PTIR permalink paths now redirect to the identical path at https://paco.io, and /ptir/ redirects to https://paco.io/ptir/.

A dedicated paco.org migration quality gate verifies:

exactly 23 historical PTIR source posts;
each source permalink maps to the corresponding paco.io URL;
PTIR metadata remains explicit;
the legacy PTIR category does not return;
the paco.org PTIR landing route points to paco.io.

Publishing automation

The active PTIR scheduler was updated after both destination and source deployments succeeded.

Future runs now:

research and verify the edition;
publish the public edition to idtprof/paco.io;
use operated-publication metadata (publication: PTIR, series: PTIR, content_type: operated-publication, ai_assisted: true, editorial_mode: operated);
use a neutral public voice on paco.io rather than addressing Francisco directly;
email the personalized HTML edition to ptir@paco.org;
never create a new PTIR post in idtprof/pacodotorg.

Validation

The migration was staged on a dedicated branch before production.

The migration validator confirmed:

full Jekyll build success;
23 migrated post files;
/ptir/ output;
/ptir/feed.xml output;
first and last historical edition routes;
exactly 23 Atom feed entries;
archive discovery of both the inaugural and latest historical editions.

The verified migration branch was merged as paco.io commit 3f5d386a0f7d0830993a47d6bdda792be8390c02, and its GitHub Pages build and deployment both completed successfully.

The paco.org continuity cutover was merged as commit 53fc3cc05e4f8926e3b9871c465f9ec16ab1b959; its existing editorial/experience gate, new PTIR migration gate, Jekyll build, and Pages deployment all completed successfully.

Cleanup

Temporary one-shot migration workflows, triggers, and branch-only validation machinery were removed from paco.io after successful production deployment.

Privacy and provenance

No EI-1 historical DELETE material was used as a migration source. The protected Ben/Sophie corpus and excluded associated media remain outside production and migration workflows.

Remaining EI-7 work

EI-7.6 should now concentrate on ecosystem-wide cross-domain navigation, canonical ownership cues, and remaining legacy/duplicate routes beyond PTIR. EI-7.7 should perform final route, feed, deployment, authorship, and duplication validation across paco.org, idtprof.net, paco.io, and read-only firg.xyz.

PACO.IO