[EI-7.1 — Multi-Site Responsibility Audit]

EI-7.1 — Multi-Site Responsibility Audit

Status: COMPLETE Date: 2026-08-08

Repositories inspected

idtprof/pacodotorg → paco.org
idtprof/idtprofnet → idtprof.net
idtprof/paco.io → paco.io
idtprof/portal → firg.xyz

High-level finding

The four repositories currently overlap because each grew from a different point in the user’s technical and publishing history. The correct separation is by purpose and authorship, not by subject taxonomy.

Recommended responsibility model

Property	Primary role	Keep here
paco.org	The person / authored publication	Blog, biography, CV, portfolio, The Loudmouth, personal/professional history, authored essays on any subject
idtprof.net	The instructor / instructional site	Lessons, course workspaces, schedules, teaching resources, student-facing instructional material
paco.io	The lab / operated publication system	PTIR, tools, experiments, digital garden, projects, automated or AI-assisted publications
firg.xyz (`portal`)	Operational teaching portal	Fast links into institutional systems, current course operations, instructor workflow shortcuts

Repository evidence

paco.org

The site has already been modernized around personal authorship, professional identity, history, and curated writing. EI-6 separated PTIR structurally from authored writing, but PTIR still shares the same domain and therefore still creates authorship ambiguity.

Decision: paco.org remains the canonical home of Francisco-authored blog material and historical/professional identity. Technology and Teaching remain valid subjects on paco.org when the material is authored personal/professional writing.

idtprof.net

The repository is a Jekyll site whose configuration still describes itself generically as Web Developer from Somewhere, while its actual current content includes a Lessons & Courses area and an active Fall 2026 ITSE-1329 course workspace. It also retains a blog engine, CV, links, and a historical _posts corpus dating back to 1985 and the 2010s.

The homepage currently loops over site.posts, so idtprof.net still behaves partly like a personal blog even though its strongest current purpose is instructional.

Decision: idtprof.net should become explicitly instructional/professional. Its legacy personal blog corpus requires classification before removal or migration; it must not be mass-deleted without checking for unique authored material or URLs worth preserving.

paco.io

paco.io already describes itself as a retro-themed personal workspace and digital garden backed by Obsidian and GitHub. Its homepage explicitly presents a vault, tools, experiments, RSS, source code, and a playful lab-like identity. The current vault is small but the architecture is appropriate for an operated publication and project environment.

Decision: paco.io is the strongest destination for PTIR. PTIR can become a distinct publication inside the lab/digital-garden property without being mistaken for Francisco-authored personal writing.

firg.xyz / portal

The portal repository’s CNAME is firg.xyz. Its README defines the site as a lightweight access point for course materials, tools, and resources. The live interface is titled F. Rodriguez | ECC and includes direct shortcuts to Gmail, Outlook, Teams, Brightspace-related workflows, and current course operations.

This is not presently a general historical predecessor site; it is an operational teaching dashboard.

Decision: keep firg.xyz operational and separate from public instructional publishing. idtprof.net should contain durable student-facing lessons/resources; firg.xyz should remain the fast operational portal. Historical references to portal.md as a conceptual predecessor can still be preserved on paco.org/paco.io, but the current portal repository should be governed by its actual function.

Overlap and conflict inventory

1. paco.org vs. idtprof.net

Both can contain Technology and Teaching material, but the distinction should be intent:

authored essay/reflection → paco.org
lesson/course workspace/student resource → idtprof.net
operational faculty shortcut/dashboard → firg.xyz

2. paco.org vs. paco.io

The key conflict is PTIR. PTIR is not Francisco-authored work and should not remain in the personal Blog stream or be presented as representative writing.

authored blog/essay → paco.org
generated/AI-assisted briefing, tool, experiment, project → paco.io

3. idtprof.net vs. firg.xyz

Both currently serve teaching, but at different layers:

durable public instructional content → idtprof.net
current operational links and workflow shortcuts → firg.xyz

4. Historical personal posts on idtprof.net

The repository contains older personal/blog posts that may overlap paco.org or represent unique material. They require an inventory before idtprof.net is narrowed to teaching.

No migration or deletion is approved by EI-7.1.

Domain rules

Use these rules when classifying future material:

Who authored it? If it is Francisco’s authored personal/professional writing, default to paco.org.
Who is the audience? If it exists primarily to teach students, default to idtprof.net.
Is it an operated system/publication? If generated, automated, experimental, or tool-like, default to paco.io.
Is it an operational shortcut? If it primarily connects the instructor to live institutional systems, default to firg.xyz.
Topic is not ownership. Technology and Teaching are subjects, not domain assignments.

EI-7.2 implications

The next sprint should restore Blog on paco.org as the chronological authored stream while retaining Subjects and Featured as separate discovery mechanisms.

Before deleting PTIR from paco.org, EI-7.2 should only remove PTIR from authored navigation/feed logic and prepare the boundary. Actual PTIR extraction belongs to EI-7.5 after paco.io’s destination architecture is ready.

EI-7.3 implications

idtprof.net requires its own editorial inventory. The immediate issues are:

stale generic site description;
homepage built as a personal post stream;
active instructional lesson area;
legacy CV/links/blog pages overlapping paco.org;
historical _posts that may duplicate paco.org or contain unique authored material.

EI-7.4 implications

paco.io is structurally ready to receive a PTIR section, but its current identity should be revised from only personal workspace and digital garden to a broader lab/publication model before migration.

EI-7.5 migration prerequisite

Before PTIR moves:

inventory every PTIR post and current paco.org URL;
identify RSS/feed behavior;
identify automation/publishing dependencies;
establish paco.io destination URLs;
determine redirects or transition stubs on paco.org;
preserve historical publication dates;
explicitly label PTIR authorship/production model.

Result

EI-7.1 is complete. No cross-domain content move has been executed. The architecture is sufficiently clear to begin EI-7.2 on paco.org without prematurely modifying idtprof.net, paco.io, or firg.xyz.

Next sprint: EI-7.2 — paco.org Authored-Publication Model.