# Research University release and domain activation

Prepared 14 October 2026 (UTC). Publication uses the existing public JournalOS project; the existing journal, superintendent and application domains are retained.

## Current operational setup

Open the private, live checklist at https://journal.research.university/university/operations#readiness. It reads current policy evidence, appointment currency, published curriculum and cohort windows and links to each responsible workflow. Recorded status does not establish institutional launch approval. LMS vendor testing, genuine legal and financial evidence, and demonstrated backup restoration require separate verification. No percentage or automatic accreditation judgment is generated.

## Review now

- VR University: https://journal.research.university/university
- Research University Press: https://journal.research.university/press
- Research intelligence: https://journal.research.university/press/intelligence
- Learning portfolios: https://journal.research.university/learn
- Academic program catalog: https://journal.research.university/university/programs
- Student portal: https://journal.research.university/university/student
- Academic services: https://journal.research.university/university/academics
- Institutional operating evidence: https://journal.research.university/university/operations
- Actual adopted policies: https://journal.research.university/university/policies
- Faculty curriculum: https://journal.research.university/university/curriculum
- Private institutional review: https://journal.research.university/institutional-review
- Framework and institutional strategy: https://journal.research.university/university/standards

## Final addresses

- https://virtual.research.university
- https://press.research.university
- https://virtual.research.university/learn
- https://virtual.research.university/institutional-review

Both new hostnames are registered at the host and pending DNS activation. The host permits five custom domains; these two plus the existing three use all five. Learning and institutional review therefore use university paths.

## Namecheap records

After reviewing the published release, open research.university → Advanced DNS. Add the following exact records. The Host field below is relative to research.university. Use Automatic TTL. Remove a conflicting A/AAAA/CNAME record at a new hostname only if one exists; retain unrelated DNS and the three existing domain configurations. Save changes.

| Type | Host | Value |
| --- | --- | --- |
| CNAME | `virtual` | `custom-domains.chatgpt.site.` |
| TXT | `_openai-site-verification.virtual` | `openai-site-verification=4MpiXW3MLatbyFHxoNk3mr2B2VkX2cqf8QEdtUAuTaI` |
| TXT | `_cf-custom-hostname.virtual` | `adc400d8-ed41-46a8-9c0f-e048209e2593` |
| CNAME | `press` | `custom-domains.chatgpt.site.` |
| TXT | `_openai-site-verification.press` | `openai-site-verification=Ec0GGQrqaajkh1Y4XfHUJsLMNvPU1vykXe813NKawqM` |
| TXT | `_cf-custom-hostname.press` | `80a3ef7a-d929-4892-bbed-5e1680f9aa0f` |

Recheck public CNAME/TXT resolution and the hosting custom-domain status. Do not announce either new address as live until the host reports active routing and SSL and HTTPS loads successfully. No Namecheap records have been changed by this release.

## First institutional setup

1. Dr. Cheteni signs in with the authenticated ORCID account or existing authorized ChatGPT account, then opens Institutional review.
2. Appoint registered quality reviewers. Software appointments do not create legal board, faculty or officer credentials. Faculty, admissions and registrar access each require a current independently reviewed appointment/qualification exhibit. A person may hold separately evidenced roles; self-assessment and self-approval remain blocked. External review access is read-only and time-limited.
3. Upload genuine authority, mission, governance, finance, policy and personnel records. Exhibits retain hashes and require independent review. Never put private student/support narratives into the institutional room.
4. Actual faculty design course outcomes and rubrics; a different appointed faculty member approves them. Build the program from exact approved course versions, prerequisites, required/elective learning units and explicit introduce/develop/master outcome mappings. A different faculty member approves the curriculum; a separate registrar publishes it after actual policy adoption.
5. Preserve the exact institutional admissions, privacy, assessment, complaints and research-integrity policy text with genuine reviewed adoption exhibits. A different quality reviewer verifies actual adoption. Additional academic freedom, accessibility, retention and research-ethics policies are supported. Templates and software permissions cannot establish adoption.
6. Registrar opens real adult university cohorts, assigns qualified advisors and schedules approved course offerings. Applicants save private drafts, optionally dictate and use writing prompts, connect their own verified ORCID, and submit. Independent admissions decisions reserve finite seats; learners explicitly accept the specific offer and preserved requirements.
7. Learners enroll in available offerings after documented prerequisites. Each offering has its own private portfolio and frozen outcomes/rubric. Faculty read and assess the exact source. Both source and judgment are preserved and hash-checked. A different registrar approves a final course judgment; older records are never overwritten by a correction.
8. Assigned advisors document feedback and program-outcome mastery against actual approved source evidence. A different registrar verifies that evidence before issuing a **nondegree** learning record. Learning units are not transferable college credit. Degree proposals remain private planning records; no degrees are published or awarded by this release.
9. The student portal contains actual application decisions, course progress, assessment feedback, records and messages. Learners can print/PDF their application, progress and learning record, export their own paginated JSON, and choose expiring/revocable verification links. Private records are never publicly shared by default. No email-delivery service is configured.
10. Academic appeals use the exact preserved original assessment and an independently appointed faculty reviewer. A remand requires a new preserved judgment and a different registrar approval. Dependent completion records are superseded when qualifying course evidence changes.
11. A learner explicitly chooses a suitable journal and authorizes a private manuscript/Paper Agent from assessed work. All contributors must authenticate ORCID and confirm actual authorship before human editorial review. Academic assessment and program completion never automatically publish a paper.
12. Registrar can close/reopen intake or offering registration within the existing approved windows and retire a catalog. Existing accepted offers retain their expiry; enrolled students keep their curriculum, delivery, work and records. No retrospective calendar/credit rewrite is performed.
13. Institutional operations shows actual aggregates with stated denominators, recorded mastery, appointment/evidence currency and preserved exhibit integrity scans. These private metrics contain no student names, ORCID identifiers, essays, personal notes or support statements. A storage integrity check does not establish backup or successful restoration.
14. Record actual program/service reviews and improvement decisions. Closure requires separately reviewed implementation and later-outcome exhibits. Download protected institutional snapshots and complete paginated inventories. Packets include design/policy/cohort metadata but exclude individual student records and academic audit events.

See `/university/academic-operations.md` for the workflow and API inventory. The original VR School/AAR application remains separate at https://apply.research.university; under-18 and K–12 applicants are not moved into adult university admissions. The school retains its existing tuition terms. The university pathways configured here have $0 tuition in the current no-revenue model; no payment system was added.

## ORCID production dependency

Identity authentication is implemented. Direct work writes remain disabled until valid production **ORCID Member API** client credentials are configured securely and each researcher grants `/activities/update /read-limited`. Public API `/authenticate` credentials do not permit work writes. See ORCID_SETUP.md. Never put a client secret in browser code or a manuscript.

The agent work is a separate interactive resource (`online-resource` API type), crediting Dr. Cheteni’s JournalOS contribution and linking to the actual agent. Original articles retain original authorship and source identifiers. Record-wide serialized reconciliation uses put-codes, handles revocation/rate limits and stops at the registry's 10,000-work ceiling. No direct ORCID writes were performed for this release.

## LMS deployment dependency

This release implements signed LTI 1.3 launch verification plus explicit account linking and portable JSON learning evidence. Register each actual LMS deployment in Institutional review. Configure exact production HTTPS endpoints, issuer/client/deployment and JWKS. The bridge consumes launches; it is not an LMS, grade-passback service, roster sync, or 1EdTech-certified integration. Do not claim universal vendor interoperability before real vendor testing.

Use one stable origin throughout an LTI launch and its account-linking flow. Cookies and client registrations are origin-bound. The existing ORCID identity client redirects unconfigured origins to its configured canonical sign-in host. For an ORCID-based LMS pilot, use a currently configured ORCID callback origin for both launch and account linking. Before running the pilot entirely on virtual.research.university, register `https://virtual.research.university/api/auth/orcid/callback` with ORCID and add that exact URL to the secure server setting `ORCID_ADDITIONAL_REDIRECT_URIS`, preserving existing values. Test the complete login/launch/link flow on the same final origin; a successful signature test alone does not verify this browser/provider flow. ChatGPT sign-in can also be tested on the final origin after DNS/SSL activation. ORCID Member OAuth remains registered to the journal callback described in ORCID_SETUP.md; do not silently change its redirect URI when activating the university domain.

## Verification

- TypeScript type checking.
- 90 JournalOS workflow checks, 19 ORCID authentication/security tests and 18 school/admissions tests.
- 49 foundation university workflow checks and 17 LTI cryptographic checks (66 total), plus 169 extended full academic lifecycle checks (235 university checks; 362 checks across the four workflow suites).
- Extended checks cover policy adoption, exact curriculum mapping, finite seats, versioned admissions decisions, role expiry, independent grading/registrar approval, source and judgment tamper rejection, completion, private exports, actual metrics, sharing/revocation, appeals and concurrent stale-write rejection.
- Catalog rights/source/hash/agent validation for 2,619 additional source records and 100 licensed APA source records; the other 100 APA discovery records are excluded from ready ingestion.
- Production build and native deployment, followed by public-route and anonymous protected-endpoint HTTP checks.

Automated workflow tests use isolated SQLite/R2 and synthetic actors. They do not create real students, faculty, courses or institutional evidence. Browser UI and actual ORCID Member/vendor LMS integration remain unverified in this environment. Catalog validation checks stored evidence and source assets; it is not a fresh publisher-wide retraction/license audit.