TRUST AND PRODUCT BOUNDARIES
Current facts, visible limits, responsible use.
Airchor is a live planning and assessment workspace. This page separates current product behaviour from future direction, advisory output from verified fact, and confirmed boundaries from claims Airchor does not make.
CURRENT PRODUCT BOUNDARY
Planning and assessment- LIVE Persistent personal workspace
- LIVE Two deterministic document routes
- ADVISORY Readiness and uncertainty labels
- LIMIT No autonomous execution or certification
01 · WHAT IS LIVE TODAY
Airchor MVP v1.0 is live by invitation.
The current release structures user-provided project context into persistent planning, assessment, roadmap, and developer-handoff documents. It provides two starting points and keeps current capability distinct from the longer-term orchestration vision.
- Access
- Invitation-based access to Airchor MVP v1.0.
- Workspace
- Invited users sign in to an authorised personal workspace.
- Two routes
- Create New Project and Work on Existing Project.
- Persistence
- Projects and generated documents persist within the authorised workspace.
- Generation
- Saved project inputs and deterministic templates produce the current document packages.
- Downloads
- Eligible generated documents can be downloaded individually as exact saved Markdown.
02 · AUTHENTICATION AND WORKSPACE BOUNDARY
Invited users work inside an authorised personal workspace.
Authentication gates the application. Saved projects, workflow state, and generated documents belong to the authorised workspace, and eligible downloads require authenticated access. This product boundary is not a security certification or a statement that every possible authorisation condition has been formally proven.
03 · PROJECT INFORMATION AND GENERATED OUTPUTS
Outputs depend on the context people provide.
Create New Project organises supplied planning context into a deterministic 14-document Blueprint Draft. Work on Existing Project organises supplied project context, evidence, findings, risks, and constraints into a deterministic 10-document assessment and recovery package.
Generated documents remain drafts for review. Their usefulness and accuracy depend on the completeness and quality of the saved project information.
04 · READINESS AND UNCERTAINTY
Labels make uncertainty visible; they do not remove it.
- Readiness
- Whether the saved project context supports the intended next use.
- Confidence
- Rule-based support from the current saved information.
- Evidence strength
- The quality, freshness, and conflict state of user-provided sources.
- Risk
- Warnings, blockers, conflicts, and declared project risks.
- Assumptions
- Beliefs that still require confirmation.
- Missing information
- Absent records, decisions, evidence, or access needed for stronger reliance.
- Recommended next action
- The first useful step selected from the current project state.
These indicators are advisory and do not independently prove technical, security, or production readiness.
Readiness, confidence, evidence strength, risk, assumptions, missing information, and recommended next actions are advisory. They do not independently prove technical, security, legal, financial, or Production readiness.
05 · RESPONSIBLE-DATA GUIDANCE
Keep sensitive and unauthorised material out of Airchor.
Use the minimum high-level project context needed for planning and assessment. Do not submit:
- Passwords
- API keys
- Tokens
- Private keys
- Database connection strings
- Private source code
- Repository archives
- Raw Production logs
- Regulated personal data
- Unauthorised client information
Airchor does not currently represent the product as an approved confidential-data, regulated-data, source-code, credential, or Production-log intake system.
06 · CURRENT LIMITATIONS
Planning and assessment are live. Autonomous execution is not.
Structure today. Governed execution is the next phase.
Airchor MVP v1.0 is a planning and assessment product. The current product prepares clearer project context and handoff drafts.
- Planning and assessmentLive today
- Automatic source-code inspectionNot current MVP functionality
- Code execution or automatic repairNot current MVP functionality
- User-project test or build executionNot current MVP functionality
- Pull-request creationNot current MVP functionality
- Project deploymentNot current MVP functionality
- Technical, security, or production-readiness certificationNot current MVP functionality
The current product does not autonomously inspect repositories, execute code, repair software, run user-project tests or builds, create pull requests, deploy projects, or certify technical, security, legal, financial, or Production readiness.
07 · PRODUCT UPDATES BOUNDARY
Product Updates are separate from application access.
Joining Product Updates submits an email address and explicit consent through the marketing website to begin Brevo double opt-in. It does not request or grant an Airchor application invitation. A subscription remains pending until the recipient confirms it.
Review Product Updates08 · SECURITY AND COMPLIANCE BOUNDARY
Scope is not certification.
Airchor does not claim SOC 2 or ISO certification, blanket GDPR compliance, a security audit, penetration testing, vulnerability scanning, specific encryption guarantees, data residency, backup or disaster-recovery commitments, incident-response times, uptime, enterprise security, or formal retention and deletion periods.
Affirmative security-control, certification, provider, retention, deletion, and transfer statements require separate evidence and approval.
09 · LEGAL AND CONTACT LINKS
Legal structure is available for review, not yet approved for Production.
The Privacy, Terms, Imprint, and Impressum routes are explicit legal-review drafts. They are not final notices or accepted terms.
10 · CURRENT PRODUCT