# QCS

> QCS is an enterprise automation engineering company specializing in agentic automation, sovereign technology architectures and open-source business systems.

## Core Capabilities

- [Agentic Automation](https://quarkcs.io/agentic-automation.md): QCS engineers governed AI agents that interpret context, call approved tools and route exceptions to people, inside real enterprise systems.
- [Sovereign Technology](https://quarkcs.io/sovereign-technology.md): QCS designs architectures where data is exportable, interfaces are documented, and no proprietary service is structural.
- [Open Business Systems](https://quarkcs.io/open-business-systems.md): QCS builds ERP, CRM, DMS and industry applications on open foundations the client's own team can extend.
- [Enterprise Integration](https://quarkcs.io/enterprise-integration.md): QCS connects APIs, documents, databases and legacy platforms so automation works across the business rather than inside one silo.
- [Private AI](https://quarkcs.io/private-ai.md): QCS deploys and governs AI models inside the client's own boundary, with routing, evaluation and observability built in.

## Reference Architectures

- [Agentic RFQ-to-Quotation](https://quarkcs.io/automation-blueprints/rfq-to-quotation.md): Enquiries arrive as unstructured email and messages. Turning them into quotations means reading intent, matching products, checking stock and applying commercial policy — work that is slow, repetitive and easy to get subtly wrong.
- [Invoice to Approved Draft](https://quarkcs.io/automation-blueprints/accounts-payable.md): Supplier invoices arrive as PDFs and scans. Matching each against purchase orders and receipts, applying tolerances and chasing the genuine exceptions consumes most of an AP clerk's day.
- [Own the Stack](https://quarkcs.io/automation-blueprints/sovereign-enterprise-stack.md): Every layer adopted without an exit path becomes structural. Years later the question 'can we move?' has no good answer, and the cost of finding out is a rewrite.
- [Request to Dispatch](https://quarkcs.io/automation-blueprints/service-operations.md): A service request has to be understood, enriched with asset and contract history, checked against SLA and parts availability, and assigned — before anyone can actually fix anything.

## Technologies

- [Framework M](https://quarkcs.io/framework-m.md): Framework M is an open-source, metadata-driven Python framework whose DocTypes generate REST APIs, permissions and schema, built for agent-readable enterprise applications.
- [Frappe Framework](https://quarkcs.io/frappe-framework.md): Frappe is a mature metadata-first framework for transactional business applications where records, permissions, workflows and reports matter.

## Industries

- [Automotive](https://quarkcs.io/industries/automotive.md): QCS builds dealership, aftersales and parts operations on open systems, then automates the coordination between them.
- [Manufacturing](https://quarkcs.io/industries/manufacturing.md): QCS implements costing, process and operational control around how a factory actually runs, not around how the software expects it to.

## Insights

- [How we built quarkcs.io so any agent can extend it](https://quarkcs.io/insights/building-quarkcs-io-for-agents.md): quarkcs.io is a website designed to be operated by agents QCS does not control. Framework M holds content and policy, Astro serves static HTML, and a scoped tool interface lets any agent draft and propose changes while a person retains the only publish authority.

## Notes

- Every page above is also available as HTML at the same URL without the .md suffix.
- Structured JSON for any page: https://quarkcs.io/api/public/{collection}/{slug}.json
- Full URL list: https://quarkcs.io/sitemap.xml