Business Basics of Qiqi Service Industry ERP
Qiqi Service Industry ERP (also known as Qiqi Management Cloud) targets productive service enterprises, with project-based operation as an important main line, connecting customers and contracts, project execution, revenue and costs, receipts and payments, financial accounting, and operation analysis to form a traceable business-finance fact chain.
Product capability domains are used to understand user intentions and find business objects, and do not prove that the current enterprise has enabled relevant modules. The actual available objects, fields, actions, and permissions of the current enterprise must be confirmed by runtime.
Authoritative Fact Principle
- First identify business facts, then locate the objects and records that carry the facts. Similar names, identical amounts, or identical dates cannot prove that two records represent the same fact.
- Distinguish between stages such as archives, plan or budget, application, contract or order, execution, confirmation or settlement, invoicing, receipts and payments; do not use the previous stage to replace the latter stage, nor infer in reverse.
- Distinguish between main objects, details, references, and associated collections. Stable IDs are used to prove record identity, and display names are only used for understanding and candidate disambiguation.
- Distinguish between record status and business facts. The status indicates which stage the record is in, and does not automatically prove that the amount has been confirmed, invoiced, received/paid, or settled.
- Take the stable definition of the product as the basis for interpretation; leave the current enterprise's objects, fields, enumerations, permissions, and configurations to be confirmed by runtime metadata and returned facts.
Fact Judgment Framework
Judge in sequence before answering or taking action:
- Which business subject and business stage the user cares about.
- Whether the target is current archives, plan caliber, process documents, or results that have occurred or been confirmed.
- Which original facts support the required conclusion, and which content is only derivation or suggestion.
- Whether there are confirmable record references, project attribution, business periods, or other stable relationships between facts.
- Whether the data scope, permissions, and integrity are sufficient to support the conclusion; when insufficient, clearly state the unknown, and do not write "not found" as "not occurred".
Time Semantics
Natural days, precise time points, moments in a day, natural months, and natural years in business have different semantics. The specific field semantics and external format must be confirmed by the current runtime metadata.
Do not replace business dates with creation time, do not fill in unexpressed business dates with the current date, and do not guess time semantics based on field names or implementation experience.
On-Demand Reading
- When you need to understand Qiqi's product positioning, main capability domains, and cross-domain business relationships, read product-capability-map.md.
- When you need to understand object categories, master-detail tables, or status life cycles, read business-model.md.
- When you need to understand project-based business-finance stages and statistical caliber boundaries, read core-business-concepts.md.
- When you need to find standard object candidates, read standard-object-catalog.md.
- When you need to understand public fields, references, enumerations, null values, or time semantics, read common-data-conventions.md.
Only read the reference files required for the current task.