Verify the material before integrating.
Use this guide to prepare product evidence, read concept studies and plan a handover. No installation commands are provided without verified product documentation.
Product documentation status
A verified CondorAdmin repository, license, runtime requirements and release history have not been supplied. A reliable setup or upgrade procedure cannot yet be published.
Once those materials exist, match documentation to the release and reproduce setup in an isolated environment, recording failures and discrepancies.
- Required: inspectable source, licensing and maintenance notes
- Required: dependencies, configuration, migrations and upgrade history
- Required: known limits, security contact and backup guidance
Reading the demos
Commerce Lab and Agent Workbench are concept studies for discussing states, data and delivery boundaries. Their local SVG covers are illustrations, not client evidence or product screenshots.
- Read the challenge and limitations before the proposed design
- Follow associated technologies and services for context
- Turn proposed deliverables into your own acceptance questions
Preparing an integration
Supply redacted API documentation, example requests, response structures and an authentication flow. Do not submit production secrets, access tokens or sensitive personal data through the enquiry form.
- Identify environments, methods, field types and error codes
- Agree on timeouts, retries, idempotency and callback verification
- Identify who supplies test access and approves integration evidence
Handover inventory
Documentation should help the next maintainer locate configuration, run checks and restore service. Its version should correspond to the delivered source.
- Page, endpoint, role and state descriptions
- Variables, dependencies and deployment procedure
- Test commands, acceptance evidence and unverified items
- Backup, rollback, incident handling and maintenance ownership