ibloud · Oct 18, 2026 · Oct 18, 2026 · Oct 18, 2026 · Oct 18, 2026 · Oct 18, 2026
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -44,6 +44,8 @@ Skip the introductory steps if you know the workflow. Please contribute **verifi
 
 ## PIXIE — optional contributor guidance and maintenance
 
+[Join, contribute and resume with PIXIE](https://loptr-lab.github.io/training/pixie-contributors.html). The existing companion prepares reviewed GitHub checkpoint drafts and reads submitted issues to resume shared work. GitHub remains the coordination record; PIXIE does not post automatically, enroll members, or grant access.
+
 [Visit PIXIE at Break This Build](https://break.loptrlab.com/) for an optional guided introduction to projects and contribution ideas. PIXIE is **not required** for participation: contributors may use this repository's issues and pull requests directly, without providing an email address or creating another account.
 
 If PIXIE's guidance is confusing, inaccessible, outdated, broken, or links to the wrong project, please [open a public issue](https://github.com/Loptr-Lab/training/issues/new/choose) describing the affected page, steps to reproduce, expected behavior, and a proposed improvement. Mark it as a **PIXIE integration or documentation report** in the issue description so maintainers can triage it to the responsible project. This repository can track training-to-PIXIE link defects, but PIXIE's own maintainers and source repository remain responsible for changes to her application; a training issue does not authorize changing PIXIE's production deployment.

diff --git a/docs/index.html b/docs/index.html
@@ -30,6 +30,7 @@ <h1>Start with your work,<br>not a computer.</h1>
     <a class="button" href="./tracks/index.html">Find a career track</a>
     <a class="button" href="./technology-planning/index.html">Build a technology plan</a>
     <a class="button" href="./technology-planning/development-environment.html">Development equipment</a>
+    <a class="button" href="./pixie-contributors.html">Join &amp; coordinate with PIXIE</a>
     <a class="button" href="./case-study/README.html">See the worked example</a>
   </nav>
 </header>

diff --git a/docs/pixie-contributors.html b/docs/pixie-contributors.html
@@ -0,0 +1 @@
+<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>PIXIE: join, contribute and resume — Loptr Lab</title><link rel="stylesheet" href="./training.css"><link rel="canonical" href="https://loptr-lab.github.io/training/pixie-contributors.html"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / CONTRIBUTOR COORDINATION</div><h1>PIXIE stays with the work.</h1><p class="subtitle">Join a project, keep a shared checkpoint in GitHub, and resume without reconstructing the briefing.</p><nav class="actions" aria-label="Contributor navigation"><a class="button" href="https://pixie-project-companion.ibloud-ivxx.chatgpt.site">Open PIXIE</a><a class="button" href="https://ecosystem.loptrlab.com">Ecosystem</a><a class="button" href="./index.html">Training</a></nav></header><main id="main"><section class="brief"><h2>Your contributor journey</h2><ol class="journey"><li><strong>Start.</strong> Open the existing PIXIE companion, choose a project and read its repository’s contribution instructions. Training is the default starting point.</li><li><strong>Choose a task.</strong> Use “How can I help?” for a bounded suggestion. Then choose “Join &amp; coordinate” and describe the proposed task, progress, blocker and next action.</li><li><strong>Review and submit.</strong> Review the checkpoint draft and its public visibility. “Review &amp; submit on GitHub” opens a prefilled issue in that project. You submit it using GitHub; PIXIE does not post automatically or enroll you.</li><li><strong>Agree scope.</strong> Record maintainer agreement, time, credit and exit arrangements in the issue. A suggestion or issue does not itself assign a task or grant access.</li><li><strong>Keep coordinated.</strong> Add progress comments with evidence, blockers and the next action. Keep the issue URL. GitHub holds the shared history.</li><li><strong>Resume.</strong> In a later session, choose the same project, select “Resume my checkpoint” and paste the issue URL. PIXIE reads the current public issue and latest comment page. Open the full GitHub discussion for older comments.</li></ol></section><section class="panel"><h2>What persists</h2><p>Submitted GitHub issues and comments persist across sessions. Drafts are not saved until submitted. Keep the issue URL: PIXIE does not automatically remember it or read private chat history.</p><p>No email intake, automatic posting, formal membership or repository access is added. Keep private information out of public issues. Current open contribution is voluntary and unpaid.</p></section><section class="brief"><h2>Build and public-release steps</h2><ol class="journey"><li>Edit the existing companion source; preserve its Site and App identities. Keep runtime code and browser instructions aligned.</li><li>Run the companion tests, TypeScript checks and production build. Verify a checkpoint draft does not post, another session can read a submitted issue, and wrong-project URLs are rejected.</li><li>Commit/push exact source, save and deploy that source through the existing Site, then verify public HTTP/API behavior. Record source commit, saved version and deployment result. GitHub source review and Sites deployment are distinct operations.</li><li>Keep ecosystem and training links pointing to this same companion. A domain change is not required. Do not create another map or replacement service.</li><li>To distribute the ChatGPT plugin publicly, verify the supported submission path for the existing Sites App. Prepare the verified publisher identity, website/support/privacy/terms URLs, actual icons, five positive and three negative review cases, a real demo recording, country targeting, commerce declaration and release notes.</li><li>Prepare the public submission separately from the private original. Author uploads omit private App bindings and use verified MCP configuration; preserve canonical App ownership and Portal-generated bindings. Do not create a duplicate private plugin.</li><li>Configure and test the exact saved submission. The verified publisher completes legal attestations and required scans. Submit for review, publish the approved version, and verify installation and tools with a separate permitted account. A private update, public website or uploaded draft is not a public plugin release.</li></ol></section><section class="brief"><h2>Current boundaries</h2><p>The companion website is public. ChatGPT plugin distribution remains private until its public release process completes. GitHub/AT Protocol membership signup and private participant storage are not implemented by this checkpoint workflow. Reported issue content is not accepted canon or verified completion.</p><h2>Keep the existing hosting identities</h2><p>The ecosystem is the hub, training is the contributor manual, and the existing companion runs the workflow. No new domain purchase or hosting migration is required. Custom domains do not publish plugins. Do not repoint the ecosystem hostname or migrate MCP/OAuth addresses without testing.</p><p>Reconcile deployed source with the GitHub contribution source before editing; do not assume automatic synchronization. Reuse the <a href="https://github.com/ibloud/ibloud.github.io/blob/main/docs/ECOSYSTEM_ARCHITECTURE.md">canonical architecture</a> and <a href="https://github.com/Loptr-Lab/training/blob/main/docs/PIXIE_ANNOUNCER_TRACK.md">PIXIE interface track</a>.</p><a href="./pixie-contributors.md">Read the source Markdown</a></section></main><footer><p>Updated 18 October 2026. Implementation and public plugin publication are tracked separately.</p></footer></body></html>
diff --git a/docs/pixie-contributors.md b/docs/pixie-contributors.md
@@ -0,0 +1,40 @@
+# PIXIE: join, contribute and resume
+
+Updated 18 October 2026. One workflow across the existing ecosystem; GitHub holds shared contribution records.
+
+[Open PIXIE](https://pixie-project-companion.ibloud-ivxx.chatgpt.site) · [Ecosystem](https://ecosystem.loptrlab.com) · [Training](https://loptr-lab.github.io/training/)
+
+## Contributor steps
+
+1. **Start.** Open the existing PIXIE companion, choose a project and read its repository’s contribution instructions. Training is the default starting point.
+2. **Choose a task.** Use “How can I help?” for a bounded suggestion. Then choose “Join & coordinate” and describe the proposed task, progress, blocker and next action.
+3. **Review and submit.** Review the checkpoint draft and its public visibility. “Review & submit on GitHub” opens a prefilled issue in that project. You submit it using GitHub; PIXIE does not post automatically or enroll you.
+4. **Agree scope.** Record maintainer agreement, time, credit and exit arrangements in the issue. A suggestion or issue does not itself assign a task or grant access.
+5. **Keep coordinated.** Add progress comments with evidence, blockers and the next action. Keep the issue URL. GitHub holds the shared history.
+6. **Resume.** In a later session, choose the same project, select “Resume my checkpoint” and paste the issue URL. PIXIE reads the current public issue and latest comment page. Open the full GitHub discussion for older comments.
+
+## What persists
+
+Submitted GitHub issues and comments persist across sessions. Drafts are not saved until submitted. PIXIE does not read private chat history, automatically remember your issue URL, create formal membership, grant repository access or collect email addresses. Keep private material out of public issues. Current open contribution is voluntary and unpaid.
+
+## Build and release protocol
+
+1. Edit the existing companion source; preserve its Site and App identities. Keep runtime code and browser instructions aligned.
+2. Run the companion tests, TypeScript checks and production build. Verify a checkpoint draft does not post, another session can read a submitted issue, and wrong-project URLs are rejected.
+3. Commit/push exact source, save and deploy that source through the existing Site, then verify public HTTP/API behavior. Record source commit, saved version and deployment result. GitHub source review and Sites deployment are distinct operations.
+4. Keep ecosystem and training links pointing to this same companion. A domain change is not required. Do not create another map or replacement service.
+5. To distribute the ChatGPT plugin publicly, verify the supported submission path for the existing Sites App. Prepare the verified publisher identity, website/support/privacy/terms URLs, actual icons, five positive and three negative review cases, a real demo recording, country targeting, commerce declaration and release notes.
+6. Prepare the public submission separately from the private original. Author uploads omit private App bindings and use verified MCP configuration; preserve canonical App ownership and Portal-generated bindings. Do not create a duplicate private plugin.
+7. Configure and test the exact saved submission. The verified publisher completes legal attestations and required scans. Submit for review, publish the approved version, and verify installation and tools with a separate permitted account. A private update, public website or uploaded draft is not a public plugin release.
+
+## Current boundary
+
+The companion website is public. ChatGPT plugin distribution remains private until the public release process completes. GitHub/AT Protocol membership signup and private participant storage are not implemented by this checkpoint workflow. This is shared project coordination using GitHub, not a claim of an integrated AetherOS system. Reported issue text is not accepted story canon or verified completion.
+
+## Hosting and domain
+
+Keep the existing repositories and domain. ecosystem.loptrlab.com remains the hub; training remains the contributor manual; the existing companion serves the workflow. A subdomain under an owned domain normally requires DNS configuration rather than another registration, subject to the DNS provider’s plan. Custom-domain setup does not publish the ChatGPT plugin. Do not repoint the existing ecosystem hostname or migrate MCP/OAuth addresses without testing their supported configuration.
+
+## Source and maintenance
+
+The companion README carries implementation commands and release details. Before editing, reconcile the actual deployed source and the GitHub contribution source; do not assume automatic synchronization. Follow the [canonical ecosystem architecture](https://github.com/ibloud/ibloud.github.io/blob/main/docs/ECOSYSTEM_ARCHITECTURE.md) and [PIXIE interface track](PIXIE_ANNOUNCER_TRACK.md). Existing work is reused; failed retrieval is not proof of loss.
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>PIXIE: join, contribute and resume — Loptr Lab</title><link rel="stylesheet" href="./training.css"><link rel="canonical" href="https://loptr-lab.github.io/training/pixie-contributors.html"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / CONTRIBUTOR COORDINATION</div><h1>PIXIE stays with the work.</h1><p class="subtitle">Join a project, keep a shared checkpoint in GitHub, and resume without reconstructing the briefing.</p><nav class="actions" aria-label="Contributor navigation"><a class="button" href="https://pixie-project-companion.ibloud-ivxx.chatgpt.site">Open PIXIE</a><a class="button" href="https://ecosystem.loptrlab.com">Ecosystem</a><a class="button" href="./index.html">Training</a></nav></header><main id="main"><section class="brief"><h2>Your contributor journey</h2><ol class="journey"><li><strong>Start.</strong> Open the existing PIXIE companion, choose a project and read its repository’s contribution instructions. Training is the default starting point.</li><li><strong>Choose a task.</strong> Use “How can I help?” for a bounded suggestion. Then choose “Join & coordinate” and describe the proposed task, progress, blocker and next action.</li><li><strong>Review and submit.</strong> Review the checkpoint draft and its public visibility. “Review & submit on GitHub” opens a prefilled issue in that project. You submit it using GitHub; PIXIE does not post automatically or enroll you.</li><li><strong>Agree scope.</strong> Record maintainer agreement, time, credit and exit arrangements in the issue. A suggestion or issue does not itself assign a task or grant access.</li><li><strong>Keep coordinated.</strong> Add progress comments with evidence, blockers and the next action. Keep the issue URL. GitHub holds the shared history.</li><li><strong>Resume.</strong> In a later session, choose the same project, select “Resume my checkpoint” and paste the issue URL. PIXIE reads the current public issue and latest comment page. Open the full GitHub discussion for older comments.</li></ol></section><section class="panel"><h2>What persists</h2><p>Submitted GitHub issues and comments persist across sessions. Drafts are not saved until submitted. Keep the issue URL: PIXIE does not automatically remember it or read private chat history.</p><p>No email intake, automatic posting, formal membership or repository access is added. Keep private information out of public issues. Current open contribution is voluntary and unpaid.</p></section><section class="brief"><h2>Build and public-release steps</h2><ol class="journey"><li>Edit the existing companion source; preserve its Site and App identities. Keep runtime code and browser instructions aligned.</li><li>Run the companion tests, TypeScript checks and production build. Verify a checkpoint draft does not post, another session can read a submitted issue, and wrong-project URLs are rejected.</li><li>Commit/push exact source, save and deploy that source through the existing Site, then verify public HTTP/API behavior. Record source commit, saved version and deployment result. GitHub source review and Sites deployment are distinct operations.</li><li>Keep ecosystem and training links pointing to this same companion. A domain change is not required. Do not create another map or replacement service.</li><li>To distribute the ChatGPT plugin publicly, verify the supported submission path for the existing Sites App. Prepare the verified publisher identity, website/support/privacy/terms URLs, actual icons, five positive and three negative review cases, a real demo recording, country targeting, commerce declaration and release notes.</li><li>Prepare the public submission separately from the private original. Author uploads omit private App bindings and use verified MCP configuration; preserve canonical App ownership and Portal-generated bindings. Do not create a duplicate private plugin.</li><li>Configure and test the exact saved submission. The verified publisher completes legal attestations and required scans. Submit for review, publish the approved version, and verify installation and tools with a separate permitted account. A private update, public website or uploaded draft is not a public plugin release.</li></ol></section><section class="brief"><h2>Current boundaries</h2><p>The companion website is public. ChatGPT plugin distribution remains private until its public release process completes. GitHub/AT Protocol membership signup and private participant storage are not implemented by this checkpoint workflow. Reported issue content is not accepted canon or verified completion.</p><h2>Keep the existing hosting identities</h2><p>The ecosystem is the hub, training is the contributor manual, and the existing companion runs the workflow. No new domain purchase or hosting migration is required. Custom domains do not publish plugins. Do not repoint the ecosystem hostname or migrate MCP/OAuth addresses without testing.</p><p>Reconcile deployed source with the GitHub contribution source before editing; do not assume automatic synchronization. Reuse the <a href="https://github.com/ibloud/ibloud.github.io/blob/main/docs/ECOSYSTEM_ARCHITECTURE.md">canonical architecture</a> and <a href="https://github.com/Loptr-Lab/training/blob/main/docs/PIXIE_ANNOUNCER_TRACK.md">PIXIE interface track</a>.</p><a href="./pixie-contributors.md">Read the source Markdown</a></section></main><footer><p>Updated 18 October 2026. Implementation and public plugin publication are tracked separately.</p></footer></body></html>