Ownership and the existing-work check
Training maintainers own this pathway and resource accuracy; no named external facilitator or partner has been appointed. At each use, the facilitator and learner verify the selected resource’s current official instructions and availability. Maintainers review corrections before publication. Recheck at least every 90 days and before recommending an application; retire unavailable resources immediately from primary next actions.
Source: Loptr-Lab/training, docs/. The GitHub Pages API reports legacy publishing from main:/docs at the existing Training URL. The existing Vercel project is training (prj_p7K2hjDRoQWoiOaCi1g7AdZWHYzF, Loptr Lab team). It is reused for an isolated preview; no hosting migration is needed.
Unresolved public-route check: direct retrieval of https://loptrlab.com/training/ was blocked by the workspace outbound proxy (CONNECT 403). Its redirect/proxy configuration and deployed-byte correspondence could not be verified. Do not claim this change is live there. Before production approval, the owner must confirm that route reaches this Training source, or identify its actual configuration for review. No DNS, domain or production setting was changed.
No AGENTS.md exists in the Training main tree inspected at base 2f2692cb0c8475eebad6076ffc4027721a9b1a06; the connected contents lookup also returned 404. The local PIXIE repository’s AGENTS applies to its Companion changes; no Companion source was edited.
Read/reused: Training README, CONTRIBUTING, CONTRIBUTOR_SAFETY_AND_GOVERNANCE, homepage, contributor HTML/Markdown and portfolio checkpoint, accessibility overview, shared training.css/display preferences, training-plan/source-verification/technology/quote templates, Minnesota participant guidance, benefits-safe founder path, existing resource-data pattern and CI; canonical architecture and participation terms. The new page fills the missing independent-work route; its small static JSON reference is limited to that lesson. Made-Sick retains general resource discovery, 50 Ways retains rights/agreements context, and each project retains its source, licensing and review authority.
Open PRs inspected with discussions: #55 local Library, #52 contributor orientation, #50 Polyfork resources, #47 optional sign-in and #38 cinematic learning. Preserve those review and device-acceptance gates. This change does not activate their features.
Guide a learner through one route
- Ask what they want to make, what blocks it and what functional access needs matter. Let them choose a contribution, paid client task or business-support conversation. No new enrollment, account, diagnosis collection or placement promise.
- Reuse the learner’s existing project checkpoint for public-safe contribution evidence. Use a private client record for proposals, contracts and correspondence. To request learning help, use the existing Training improvement issue route with a sanitized question; support capacity must be agreed, not assumed.
- Before an external collaboration, the learner uses the organization’s published process to ask about a bounded proposal. A directory listing or initial reply is not a partnership. Only an authorized representative’s explicit written agreement establishes the arrangement.
- Record scope, deliverables/exclusions, dates and time limit, named supervisor/reviewer, accessibility support, review points, credit, compensation or unpaid status, rights/licensing, permitted disclosure, acceptance criteria and exit terms. Reuse existing governance and participation guidance; a paid commission requires a separate signed agreement before work. Obtain qualified advice where needed; this guide creates no legal terms.
- Review evidence in the adapted training-plan fields. Check personal contribution, sources, AI assistance, access checks, reviewer feedback, artifact/version and unfinished work. Require evidence for each proposed/submitted/accepted/deployed status. Confirm display permission and redactions before portfolio publication. A merge is not deployment or employment.
No organization was contacted, no application submitted, no learner information shared and no partnership announced as part of implementation. Neither a facilitator nor an AI may infer those permissions from this handoff.
Maintain the source reference
Edit independent-work-resources.json, then run the renderer below. Records use the existing resource pattern’s name, URL, status and reviewed context with pathway-specific eligibility, geography, contact route, confirmed facts, proposal and unknowns. There is no database or runtime lookup. The rendered HTML works without JavaScript.
- Open official contribution/application/contact sources and read the relevant policy; record the exact URL, check date, scope and confirmed claim. A successful HTTP request alone is not validation. Check actual intake and vacancies separately.
- Separate confirmed services from a proposed partnership. Keep unknowns explicit.
lastChecked: nullandstatus: recheck-requiredmean no current confirmation.lastAttemptedrecords an attempted retrieval, never a successful check. - At this review, Mirlo and Picard contribution instructions were read. Other supplied official pages were blocked by the network proxy. They remain prior research with no new confirmed facts. Recheck those sources before relying on them; this preview does not satisfy current-opportunity acceptance for those entries.
- For stale or inactive resources, move them to
group: adjacentor retire the recommendation, retaining a dated reason and source history in Git. Reconcile Resonate (closed as of 2026), Ampled (closed 2023) and the located UnFound 2023 intake. Do not promote old listings to current roles. - Making Space includes freelance/contract research; FAU AccessTECH paid internships/portfolio and BIT paid apprenticeships are employment-adjacent. Melwood abilIT is disability-focused training/employment support. Kevuru has no verified graduate-client pathway; Subvert has no verified open developer/graduate partnership; Guilded’s client-finding/referrals are unconfirmed; Catchafire is volunteer work. These are supplied research corrections pending direct official recheck, separated from primary actions. Confirm exact program/contact URLs, including FAU and BIT identity, before recommending them.
- Submit corrections through the existing Training issue/PR process with source evidence, no private data. Maintainers review scope, accuracy and availability; no automatic publication or invented organizational commitment.
Build and verify
From the Training repository root, with Node 20+ and Python 3:
npm ci --ignore-scripts --no-audit --no-fund
node scripts/build-independent-work.cjs
node scripts/build-independent-work.cjs --check
node --test test/independent-work.test.cjs
npm run typecheck
node scripts/build-threshold.cjs --check
node scripts/build-threshold-handbook.cjs --check
node --test test/threshold.test.cjs
node scripts/validate-ai-literacy.cjs
npm test -- --runInBand
python3 -m http.server 8765 --bind 127.0.0.1 --directory docs
In a second terminal, using existing external browser-test tooling (do not add application dependencies):
NODE_PATH=/path/to/test-tools/node_modules \
BROWSER_EXECUTABLE=/path/to/chromium \
AXE_PATH=/path/to/axe.min.js \
node scripts/test-independent-work-browser.cjs
The browser test walks homepage → pathway → all three routes, contributor navigation, resource disclosures, evidence download and handoff; checks keyboard focus, local links/anchors, no-JavaScript access, reduced motion, doubled text/reflow at phone/tablet/desktop widths, both themes, axe A/AA and absence of unexpected external requests. Existing Jest starter methods intentionally throw Not implemented; report those failures separately, as the existing CI does. Do not edit starter tests to manufacture a pass.
Physical Safari/iPad, VoiceOver and real learner/facilitator acceptance are not tested by browser emulation. They remain manual acceptance checks. Verify current external services and the public custom-domain route separately.
Preview and deployment
- Commit only the scoped source, renderer, handoff and checks on
feat/independent-work-pathway. Push that implementation branch and open a draft PR against main. Never push directly to main. - Reuse Vercel project
trainingunder teamloptr-lab. Create a preview from that exact branch/SHA (Git source typegithub, repository ID1290286392). For a deployment-specific override, use no framework, no install/build command and output directorydocs. Do not change project-wide settings or production aliases. Check READY state and HTTP responses at/independent-work.htmland/independent-work-handoff.html. - Keep existing Vercel access protection. The owner may need to sign in to view the preview. Record the immutable URL, deployment ID and SHA in the PR. Direct workspace browser access may be blocked; authenticated Vercel fetch can verify returned bytes, but a local replay is not a hosted-browser test.
- Before merge or production publication, resolve current-source/availability checks, verify custom-domain ownership/routing, review physical accessibility observations and obtain explicit owner approval for this change. Passing CI is not approval.
- Only after approval, the maintainer merges the reviewed PR. GitHub Pages publishes main’s
/docsthrough its existing legacy configuration. Verify the public homepage, pathway, handoff, assets and fragment navigation, including the custom URL’s actual mapping. If Vercel also needs a production release, obtain approval for that target and use the existing project with the reviewed SHA; do not silently promote a preview. - If acceptance fails, keep the preview under review and record the failure in the PR. After an approved release, rollback uses the existing source-review/deployment process; preserve prior reviewed commits and resource history.
The implementation report in the PR records actual command results, preview verification and outstanding gates. No production deployment or merge is authorized by this handoff.