Product feedback
Describe a workflow problem, expected result and the evidence needed to prove it is solved.
Contact TenqoraCommunity
Help shape reliable infrastructure operations.
Bring field evidence, integration requirements and product feedback into a governed process that protects physical truth and Client data.
Ways to participate
Choose the path that matches what you know.
Catalog evidence
Propose Equipment, modules, sensors or cables with manufacturer documentation and exact compatibility facts.
Review the modelIntegration proposals
Define the provider, direction, authority, data classes and security boundary before implementation begins.
Integration modelGoverned change
Evidence moves through one visible path.
State the need
Record the operational problem, affected role and expected outcome.
Review evidence
Confirm manufacturer, API or field evidence and identify unknowns.
Build a bounded slice
Implement with tenant isolation, tests and an explicit authority boundary.
Publish the change
Keep release history separate from each Client's immutable Audit History.
Open now
Follow the product without inflated community claims.
| ROUTE | WHAT IT PROVIDES | BOUNDARY | OPEN |
|---|---|---|---|
| GitHub project | Source, issues and implementation history | No Client data or secrets | Open |
| Resources | Product model, architecture and guidance | Reviewed public content | Open |
| Change Log | Released product and system changes | Separate from Audit History | Open |
| Early access | Company registration and product conversation | Every request is reviewed | Request |
Ecosystem direction
Extend the system without weakening its truth.
Discovery
Source-labelled proposals from Agents and integrations, never silent inventory creation.
Governance
Declared permissions, compatibility and rollback before an extension is trusted.
Field operations
Mobile Tasks, audits and evidence remain tied to exact infrastructure identities.
Contribute a real use case