install_first_run
Install and first run
Install Arch, start the local runtime, and complete the first guarded-repository setup without implying public packages are available before release proof is green.
public help index
Help
These topics are the public help map for install, update, license, support, evidence, and recovery paths.
This route publishes the checked help index for the current locale with 23 topic summaries.
Topics
update
Update
Explain safe update expectations, package provenance, and release-note checks without promising update automation that launch evidence has not admitted.
downgrade
Downgrade
Describe downgrade support only where package evidence and support rehearsal prove it; otherwise route the user to support.
package_recovery
Package recovery
Help users recover from failed or incomplete package installation while keeping hashes, package names, paths, and support evidence exact.
uninstall_reinstall_purge
Uninstall / reinstall / purge
Explain uninstall and reinstall paths, including what local data may remain and when a purge is irreversible.
trial_start
Trial start
State the 30-day trial, billing start, and payment-method requirement consistently with commercial terms and purchase copy.
license_activation
License activation
Guide activation using the admitted license flow while preserving helper boundaries, privacy posture, and exact license-field names.
student_eligibility_access
Student eligibility and access
Explain student eligibility, email-domain confirmation, and support routing before purchase when eligibility cannot be confirmed.
offline_grace
Offline grace
Describe license offline grace only as far as the terms and retention playbook admit, including what happens when Arch cannot reach the issuer.
first_real_repository_walkthrough
First real repository walkthrough
Walk a user through one local repository, one claim, visible evidence, visible gaps, and one governed next action without treating a work item as proof.
scan_bootstrap
Scan and bootstrap
Explain how Arch scans a guarded repository into typed records and what scan coverage is still unsupported or unknown.
admitted_source_coverage
Admitted source coverage
Name only the source coverage that admitted scan contracts and launch evidence allow Arch to claim publicly.
architecture_note_posture
Architecture-note posture
Explain architecture notes as source-grounded context where admitted, not as automatic proof of a claim.
attention_review
Attention review
Describe the attention review surface as a way to inspect claims, evidence, authority, gaps, and next actions, not as an inbox or ticket queue.
evidence_authority_views
Evidence and Authority views
Explain how Workbench shows evidence and why that evidence is allowed to count, while keeping unsupported gaps visible.
what_arch_does_not_prove
What Arch does not prove
State that Arch shows source-grounded evidence, authority, gaps, and audit trail, but does not prove empirical truth by assertion.
change_preflight
Change preflight
Explain previewing a governed change before apply, including why a dry-run receipt or apply token is not the same as final proof.
agent_context
Agent context
Explain how Arch provides bounded local context to agents through admitted operations without giving agents unsupported authority.
mcp_setup
MCP setup
Guide setup of the local MCP surface while preserving client names, protocol fields, resource URIs, and fail-closed behavior.
privacy_data_boundary
Privacy and data boundary
Explain what Arch reads locally, what it does not upload, and which helper-boundary handoffs are outside Arch copy authority.
support_diagnostics
Support and diagnostics
Tell users what diagnostic information support may request and how local data boundaries apply to that request.
recovery
Recovery
Explain how users recover from blocked or failed flows, including when Arch records why a gap remains open.
release_notes
Release notes
Publish release changes, known gaps, compatibility notes, and localization posture without treating version numbers as proof.