Resources
Articles and research for business owners
Written by Code Colonies for owners, finance heads and plant heads of growing Indian businesses. Every piece is checked against the law and against MatruOS as it works today, and the long ones are also in Hindi and Gujarati.
This month
The lead paper and the latest articles Long reads, worked from the law and from how the work is done.
Research paper · version 1.4The approval ladder: deciding how much an AI team may do without askingA method for grading each action an AI agent can take by what it reaches and whether it can be undone, and for setting the human approval each grade needs. It compares the EU AI Act, NIST, ISO/IEC 42001 and India's DPDP Act, and says plainly where MatruOS does not yet follow the method.Read the paperL0InformReads and reportsL1SuggestProposes in wordsL2Prepare and holdYou approve each changeL3Act and reportEarned, internal onlyL4Act, report exceptionsEarned, narrowest cells
ArticleBringing down days sales outstanding across a dealer networkA manufacturer selling through hundreds of dealers carries much of its working capital in their accounts. Days sales outstanding comes down when credit is visible at the order, reminders follow a fixed rhythm, disputes are separated from the account and payments are matched the day they land, and when the business uses the financing levers available to it with their cost known.ArticleClosing the books in three working days in a multi-plant manufacturerIn a manufacturer with several plants, the close is held up by information that arrives late: purchase bills still in email, transfers recorded at one plant and not the other, and stock and accruals worked out at month end. A three-day close rests on capturing each transaction once, when it happens, in one record that every plant and the head office share.
By topic
Start from the problem in front of you Each topic gathers the articles, research and case studies on it.
StockControlling batches and expiry in pharma and food distributionGet paidBringing down days sales outstanding across a dealer networkFinance and GSTReconciling GSTR-2B every month to claim input tax credit in fullAI and governanceThe approval ladder: deciding how much an AI team may do without askingAI and business valueCounting the value an AI team creates: a method that uses a business's own recordsProduction and qualityQuality checks and production costing for an auto components plantProduction and GSTJob work, lots and shrinkage for a fabric converter sending grey cloth to process housesAI operating systemsBridging the 94% Enterprise AI Value Gap: The Case for a Unified AI Operating System (AI OS)
Articles
How the work is done well The measures, the habits, the law and where MatruOS fits.
ArticleControlling batches and expiry in pharma and food distributionFor a pharma or food distributor, expired stock is written off against margin, and a batch that cannot be traced puts the licence at risk. Recording the batch and expiry at receipt, picking the earliest expiry first, watching what expires in the next 90 days and handling returns by batch keeps write-offs low and gives a recall the delivery records it needs.ArticleBringing down days sales outstanding across a dealer networkA manufacturer selling through hundreds of dealers carries much of its working capital in their accounts. Days sales outstanding comes down when credit is visible at the order, reminders follow a fixed rhythm, disputes are separated from the account and payments are matched the day they land, and when the business uses the financing levers available to it with their cost known.ArticleReconciling GSTR-2B every month to claim input tax credit in fullInput tax credit can be claimed only on invoices the supplier has reported, as shown in GSTR-2B. A monthly reconciliation that starts on the 14th, sorts every bill into matched, different or missing, and chases suppliers by credit at risk lets a business claim what it is owed by the GSTR-3B due date.ArticleTracking material at job workers and filing ITC-04 under GSTMaterial sent to a job worker stays the principal's under GST, but only within time limits: one year for inputs and three years for capital goods. A challan for every dispatch, a running balance per job worker and a watch on the due-back date keep the credit safe, and let ITC-04 be produced from the challans already recorded.ArticleClosing the books in three working days in a multi-plant manufacturerIn a manufacturer with several plants, the close is held up by information that arrives late: purchase bills still in email, transfers recorded at one plant and not the other, and stock and accruals worked out at month end. A three-day close rests on capturing each transaction once, when it happens, in one record that every plant and the head office share.
Research
How much an AI team may do, and what it is worth With sources, limits and where MatruOS falls short.
ResearchThe approval ladder: deciding how much an AI team may do without askingA method for grading each action an AI agent can take by what it reaches and whether it can be undone, setting the human approval each grade needs, and widening an agent's freedom only for reversible internal work and only on evidence from its own approved work. It sets out the statistics behind that evidence, the related frameworks it builds on, and where MatruOS does and does not yet follow the method.ResearchCounting the value an AI team creates: a method that uses a business's own recordsA method for counting what an AI team is worth from a business's own records. It separates three levels of claim (recorded, compared with the business's own baseline, and caused), gives each a test a finance head can apply, measures time saved from the business's own timings including rework, and requires every figure to carry its level, its basis and its limits. It also reports where MatruOS's own figures follow the method and where they do not yet.ResearchBridging the 94% Enterprise AI Value Gap: The Case for a Unified AI Operating System (AI OS)Individual AI assistance can leave a business dependent on disconnected stock checks, credit approvals, and manual order entry. This paper examines how a unified AI operating system could connect those activities through shared records, institutional knowledge, and controlled execution.ResearchInstitutional Memory as Operational Infrastructure: A Framework for Context Persistence, Validity, and Decision Traceability in AI Operating SystemsAn enterprise agent may retrieve an authentic document and still apply an instruction that is expired, superseded, or restricted to another customer. This paper examines how institutional knowledge becomes suitable for operational use in an AI operating system.ResearchTransactional Integrity and Agent Coordination in AI Operating Systems: Architectural Requirements Across CRM, ERP, and CommerceSeveral agents can make individually reasonable decisions that collectively exceed stock, credit, or fulfilment capacity. This paper examines the transaction boundaries required when an AI operating system coordinates customer relationship management, enterprise resource planning, and commerce.ResearchDelegated Authority and Human Accountability in AI Operating Systems: A Framework for Operational GovernanceGiving an agent access to a business application does not establish which decisions it may make or who remains responsible for their consequences. This paper develops a framework for delegated authority in enterprise AI operating systems.ResearchSecurity Boundaries in AI Operating Systems: Prompt Injection, Data Isolation, and the Protection of Execution AuthorityAn enterprise agent must read information from customers, suppliers, documents, and external services while retaining the authority limits established by the business. This creates a security problem when instructions embedded in that material influence tool use or access to protected data.ResearchFailure Propagation and Recovery in Agentic Business Operations: A Framework for Reliable ExecutionA business workflow can remain incomplete after an agent has produced a plausible response or received a successful result from one tool. Failures can occur between internal updates, external actions, and the communication of completion.ResearchThe Economics of Unified AI Operations: Workflow Costs, Coordination Overhead, and Enterprise Value AttributionThe cost of an AI workflow extends beyond model usage to implementation, supervision, exception handling, maintenance, and unresolved work. This paper develops an economic evaluation framework for enterprise AI operating systems using verified business completion as the unit of analysis.ResearchAI Operating System Adoption in Indian MSMEs: Organisational Readiness, Informal Knowledge, and Operational ConstraintsAn AI operating system requires usable records, explicit authority, and the capacity to manage exceptions after deployment. These conditions can differ substantially across Indian micro, small, and medium enterprises, even within one industry.ResearchEnterprise Transition to an AI Operating System: Interoperability, Context Portability, and Operational ContinuityIntroducing an AI operating system into an established enterprise requires decisions about which system owns each record and which service may create a business commitment during transition. This paper develops a migration framework that connects interoperability, data reconciliation, authority transfer, and recovery.ResearchEvaluating Enterprise AI Operating Systems: A Research Protocol for Execution Correctness, Control Effectiveness, and Operational OutcomesAn enterprise AI operating system should be evaluated through the business states it creates, the authority it respects, and the obligations it leaves unresolved. A fluent response or successful demonstration provides limited evidence for those requirements.
Case studies
Worked scenarios for larger businesses One business type and size each, with the figures worked in front of you.
Case study · scenarioQuality checks and production costing for an auto components plantHow MatruOS runs incoming and output quality checks and production costing for a machining plant supplying vehicle makers: lots held until checked, readings against limits, supplier bills entered against the receipt, matched to the order and held while goods are checked, and each work order costed against its standard.Case study · scenarioCollections for a ceramic tile manufacturer with a 400-dealer networkHow MatruOS runs dealer collections for a tile manufacturer selling on credit through about 400 dealers: credit checked at the order, automatic reminders before and after the due date, round-amount payments settled against the oldest invoices, breakage claims settled by credit note, and money collected after a reminder counted from the records.Case study · scenarioJob work, lots and shrinkage for a fabric converter sending grey cloth to process housesHow MatruOS runs job work for a Surat fabric converter that buys grey cloth and sends it to process houses for dyeing, printing and finishing: a challan for every dispatch, finished fabric received against the grey it used with shrinkage recorded, time limits watched, and the ITC-04 tables produced from the same records.Case study · scenarioBatch production, quality release and shelf life for a specialty chemicals makerHow MatruOS runs batch production for a specialty chemicals maker: work orders against multi-level formulations, imported raw materials costed with freight and duty and checked before use, each batch held until quality releases it, batch and expiry recorded at output, and the earliest expiry taken first.
Guides
71 plain guides for daily work Short answers on GST, getting paid, stock, staff and running the business, each with the date it was last checked.
Factory and operationsBill of materials: the recipe every factory needs · How to cost a product: material, labour and overheadsGST and taxBill of supply: when you issue one in place of a tax invoice · CGST, SGST and IGST: which one to chargeGetting paidHow to collect and track customer advances · How to get customers to pay on timeStock and buyingDead stock: how to find it and what to do with it · How to choose and review suppliersStaff and payrollA leave policy for a small business · Hiring your first employee: a checklist for Indian businessesRunning the businessApproval limits: who can sign for what · Cash flow for small business: why profit is not cashAI and dataHow to choose business software for an Indian SME · Leaving Tally: what to plan before you switchGlossaryGSTIN, HSN, ageing, landed cost and the other words on your invoices and returns, each with an example.Free toolsGST, margin, cost of credit, late fee, break-even and stock calculators, plus GSTIN and invoice series checkers. The sums run in your browser.
How we write
What every piece is held to So you can act on it, and check it.
Every figure has a sourceRates, dates and limits come from the Act, the rules, a circular or the portal. Each piece lists them at the end, with the date we checked.
Sums you can redoWhere a piece works out a saving or a cost, the sum is shown with its assumptions, so you can put in your own numbers.
Product claims checkedAnything a piece says MatruOS does is checked against the product as it works today. What is not built yet is listed under Not covered yet.
Case studies are scenariosA case study works through one business type and size. It names no client and reports no client results.
See it on your own business One system, set up for your trade.
MatruOS brings your accounts and GST, stock, sales, purchase, production and people onto one record, with Muni and an AI team on the routine work. 7-day free trial, no card needed, or book a 30-minute walkthrough set up for your business.
See plans and what each includes