NOS App Help & Product Documentation
A public entry point for understanding and using the NOS application. This section covers the current product experience; the Canonical Knowledge Guide explains the wider system, principles, and planned architecture.
Documentation stage: October 2026 Alpha. Step-by-step product tutorials and interface-specific articles will be published here as they are approved and supplied by the NOS product team. This page does not claim that those forthcoming tutorials are already published.
New to NOS? Read the complete Member & Investor overview.
How the Alpha workflow is organized
The NOS production experience begins with a Digi-Pitch, which makes a project idea visible. Discovery allows Members to explore possibilities without creating a binding work obligation. Work Cards describe defined pieces of work. An accepted Commitment establishes the explicit terms governing work. The production workflow then involves execution, deliverable submission, review, and acceptance, with project history preserved.
These are architectural and product-level descriptions, not instructions for specific buttons, screens, roles, or permissions. For accurate interface procedures, consult each feature-specific guide once published.
Read the NOS Lifecycle reference · See current Alpha status and the roadmap · Understand commitments, rights, and compensation
Product-documentation library: reserved subjects
The following is our intended library structure. These article titles identify where future documentation belongs; they do not represent live pages or imply that each feature is shipped. Articles will be linked here and added to the sitemap when approved content is actually published.
Getting started and identity
- Account creation, sign-in, and access
- Member profiles and organizations
- Project creation and Digi-Pitches
Discovery and participation
- Discovering and finding Projects
- Using Discovery
- Work Cards and applications to participate
- Team formation, roles, and permissions
Working on Projects
- Creating and accepting Commitments
- Project boards and milestones
- Deliverables, submission, review, and acceptance
- Messages and notifications
- Changes, disputes, and project completion
Accounts and support
- Payment-related workflows and records, where available
- Privacy, account settings, and account support
- Troubleshooting and frequently asked product questions
- Release notes and known limitations
Editorial rules for future product guides
- Version and status: identify the applicable release (e.g., Alpha) and last verified date.
- Source of truth: publish approved instructions from the NOS product team; do not infer interface behavior from architectural plans.
- Scope: explain what the feature does, who can use it, the exact procedure, expected result, and known limitations when documented.
- Stable URL: retain the article's public URL across routine updates; log meaningful product changes rather than renaming or duplicating pages.
- Current vs. planned: identify features that are not yet available without treating future capabilities as existing.
- Public safety: remove private Member information, account secrets, and internal-only operational details before publishing.
For any procedure that has not been documented or confirmed, consult official in-app guidance or NOS support instead of inventing steps.
Related NOS references
- Complete Canonical Knowledge Guide — full NOS architecture and glossary
- What NOS Is — purpose and differentiation
- Members & Participation — Member, Owner, Collaborator, and Backer concepts
- NOS FAQ — product and conceptual questions