Solynth · Help
Help by Responsibility
Solynth help follows the function. When a capability moves between portals, its primary guidance moves with the role that owns it.
Living Help
Choose your workspace
Shared platform principles, role-specific procedures
Membership
Member Help
Sign-in, account state, member access, member-facing services and safe use of authenticated Solynth functions.
Administration
Admin Help
Identity and access, Metadata Operations, canonical planning, reports, knowledge and Platform Health.
Operations
Operator Help
Scheduled operations, backup and recovery, routine service checks, operational evidence, regression monitoring and escalation.
Engineering
Developer Help
API credentials, `/api/v1` engineering, the canonical REST regression harness, source control, validation, deployments and data services.
REST responsibility map
Member
Account & Access
Authenticated member endpoints expose account identity, entitlement inventory and the current member-access gate. Normal members generally use the Member Portal rather than calling the API manually.
Admin
Metadata Operations
Administrative Metadata Operations under `/api/v1/admin/metadata/...` require SOLYNTH_ADMIN and remain governed administrative workflows.
Developer / Operator
Build vs Run
Developers own API contracts, validators and the regression harness. Operators own routine execution, monitoring, evidence and escalation when a deployed check fails.
Shared rules
Planning
Canonical truth
The Comprehensive Plan remains canonical. GitHub is the implementation/evidence surface for executable work; Linear and Jira are governed projections.
Security
Never publish secrets
Do not place passwords, tokens, session cookies, private keys, resolved connection strings or other secret values in help, source or evidence.
Governance
Help follows the function
When a capability changes ownership, move its authoritative help with it and retain cross-links only where they help the user navigate.