nikki-erp

Package codify derives a machine code from a human label: "Nước ngọt có ga" → "nuoc_ngot_co_ga".

Package cronexpr parses and evaluates 5-field cron expressions in UTC.

Package fpe implements format-preserving encryption.

Package json holds the JSON Schema describing a dynamic model definition, plus the validator used before a model JSON string is parsed into a builder.

Package advanced holds AdvancedPgQueryBuilder, the enhanced PostgreSQL graph query builder.

Package crockford implements fixed-width Crockford Base32 with integer arithmetic only.

Package model provides robust and easy-to-use model mapper and utility methods for Go.

Package tabular reads the first sheet of an xlsx workbook or a csv document into a header row plus string rows.

Package accounting owns tax: master data, effective-dated configuration, determination rules and the calculation engine.

Package app holds the Accounting application services: the layer that authorizes a request and then delegates to a domain service.

Package tax implements determination, calculation, rounding and reversal, applied in that order.

Package settings declares what an organization may configure about its own tax handling.

Package dynamicengines declares the thirteen tax configuration onions Accounting serves through the composable resource engine, and registers them into the dependency container during Init().

Package defaults holds the records every new organization starts with, one `<schema>.json` file per resource.

Package external binds Accounting's local ports to the services other modules publish.

Package currency publishes which currency an organization keeps its books in.

Package tax is the port other modules consume to have tax determined and calculated.

Package taxconfig declares the layers of the thirteen tax configuration resources Accounting serves through the composable resource engine at /v1/accounting/{schema_name}: a repository, a domain service carrying the lifecycle and integrity rules, and the authorized application service.

Package auditlog records who did what to which record: every mutation the composable engine performs, the reads a resource opts into, and the custom actions that report themselves.

Package dynamicengines declares the resource onion Audit Log serves through the composable resource engine, and registers it and its typed layers into the dependency container.

Package action declares the layers of the auditlog_action resource: one row per audited action.

Package transport subscribes Audit Log to the org lifecycle commands and mounts its routes.

Package commerce is one module made of three parts: inventory, purchase and sales.

Package infra binds the ports every part of Commerce consumes.

Package defaults holds the records every new organization starts with, one `<schema>.json` file per resource.

Package external binds Inventory's outbound ports to the services other modules and the core publish.

Package message speaks the broker's protocol for Inventory's integration event port.

Package external binds Purchase's local ports to the services other modules publish.

Package defaults holds the records every new organization starts with, one `<schema>.json` file per resource.

Package external binds Sales' local ports to the services other modules publish.

Package invoicing binds Sales' fiscal-document port to whoever issues the documents.

Package message speaks the broker's protocol for Sales' integration event port.

The only raw SQL of the promotion family, a deliberate exception to the engine-first rule: taking the last use of a promotion or voucher safely needs UPDATE ...

Package sequenceusage helps a Commerce part answer Essential's "is this sequence definition still in use" (usagecheck.ResourceSequenceDefinition), asked before a definition is archived.

Package app holds the Inventory application services: authorization, and the operations that span more than one domain service.

The only raw SQL in the Inventory module, a deliberate exception to the engine-first rule: reserving stock safely requires SELECT ...

Package settings holds Inventory's settings schemas.

Package dynamicengines declares the resource onions the Inventory module serves through the composable resource engine, and registers them into the dependency container during the module's Init().

Package external declares the ports Inventory consumes from other modules.

Package message is the port for Inventory's outbound integration events.

Package product is the Inventory module's cross-module port: the only Products capability other modules bind to.

Package stock is the port onto what Stock knows about a location.

Package warehouse is the contract for Warehouse operations spanning more than one resource: writes that touch a warehouse and its locations together, plus the flow reads the Stock movement engine plans against.

Package purchase covers the procurement cycle from request for quotation to confirmed purchase order.

Package app holds the Purchase application services.

Package services holds the rules of the Purchase module: the totals recomputation, the order and agreement lifecycles, and the audit trail that records them.

Package vendorpricing decides which vendor price applies to a purchase.

Package settings holds Purchase's settings schemas.

Package dynamicengines registers the composable onions of the Purchase resources and publishes their typed layers into the dependency container.

Package agreement declares the CRUD layers of the purchase agreement and its lines.

Package audit declares the CRUD layers of the purchase audit trail.

Package configuration declares the CRUD layers of the per-org purchase configuration.

Package external declares Purchase's local ports onto the capabilities other modules offer, so that splitting a module into its own process changes only the binding in infra/external.

Package order declares the CRUD layers of the purchase order, its lines and its sourcing groups.

Package vendorprice declares the CRUD layers of the vendor price list.

Package sales owns the commercial transaction: sales order and lines, pricing and promotion, billing, payment allocation, return and refund.

Package app holds the Sales application services.

Package services holds the Sales business rules.

Package pricing is the sales pricing engine: a pure function from a basket to a priced result.

Package promotion is the pure Sales promotion engine (BR_Sales_Promotion_Voucher, plan §3.1).

Package settings holds Sales' settings schemas.

Package dynamicengines declares the resource engines the Sales module serves, and creates them during Init().

Package eventhandlers acts on the events Sales subscribes to.

Package billing declares the commands the scheduler dispatches into Sales.

Package catalog declares the layers of the Sales catalogue resources: the fulfillment methods, channels and points a sale happens through, and the pricelists and combos it is priced by.

Package channel is Sales' outward-facing contract for sales channels and sales points.

Package event declares what Sales listens for on the internal event bus.

Package external declares Sales' local ports onto the capabilities other modules offer, so splitting a module into its own process changes only the binding in infra/external.

Package invoicing is Sales' port onto the issuing of legal fiscal documents.

Package fiscal declares the layers of the resources that turn a sale into a legal document: the request for an invoice, the instruction that says how to bill, and the record of each issuance attempt.

Package fulfillment declares the layers of the resources that carry out a sale: the fulfillment a confirmed order owes, the attempts made against it, and the record of a target being moved.

Package integration declares the layers of the two records Sales keeps about itself: the manual discounts granted on an order, and the outbox of integration events other systems consume.

Package message is the port for Sales' outbound integration events.

Package order is Sales' port for raising and settling an order from another module in-process.

Package promotion declares the layers of the promotion and voucher resources (BR §8): the promotion with its scope, rules, rewards and selectors; the vouchers that unlock it; and the read-only records of what a confirmed order received.

Package quotation declares the layers of the quotation resources: the offer a customer is given before it becomes a sale, and the lines it quotes.

Package returns declares the layers of the return and refund resources: the customer's request to send goods back, the lines it covers, and the money paid back against it.

Package cqrs receives the commands the scheduler dispatches into Sales.

Package eventtransport subscribes Sales to the internal event bus and dispatches each event to the handler registered for its type.

Package v1 serves the Sales resources over HTTP.

Package contacts holds the people and organizations the business deals with.

Package dynamicengines declares the resource onions the Contacts module serves through the composable resource engine, and registers them into the dependency container during the module's Init().

Package commchannel declares the layers of the contacts_comm_channel resource: the ways a party can be reached (phone, email, address, …).

Package party declares the party capability that Contacts offers to other modules.

Package relationship declares the layers of the contacts_relationship resource: a typed link between two parties (employee of, subsidiary of, …).

Package vendor declares the vendor capability that Contacts offers to other modules.

Package audit is the core port through which the platform records who did what to which record.

Package httpclienttest holds test helpers for code that calls out through the shared HTTP client: an in-memory tracer, a traced request context, and a server that records headers.

Package orglifecycle lets every module write its defaults for a new organization and remove everything it holds for a deleted one.

Package defaults reads a module's org defaults: one `<schema_name>.json` file per resource, holding an array of rows that the module writes through its domain services.

Package resourceaccess is the core port through which a module asks whether the caller may read a record of another module's resource, without importing that module.

Package settings is the shared contract every feature module writes its settings through.

Package storage is the core port through which any module tells the storage module which files its records use.

Package usagecheck asks the modules that reference a resource whether it is still in use, before the module owning it deletes it.

Package composable is the dynamic-resource engine: schema-driven CRUD, org scoping, permission, computed fields, the built-in REST route table and its param binders, split into the onion layers a feature module already has: a repository, a domain service, an application service and a REST handler, each with a default implementation a module embeds and extends.

Package sequence holds the pure algorithms behind Sequence: the pseudorandom (FF1) value, template rendering and validation, reset periods and the idempotency fingerprint.

Package settings holds Essential's settings schemas.

Package timezone is the hardcoded IANA catalogue a timezone setting is chosen from.

Package dynamicengines declares the resource onions the Essential module serves through the composable resource engine, and registers them into the dependency container during the module's Init().

Package defaults holds the records every new organization starts with, one `<schema>.json` file per resource.

Package external binds Essential's local ports to the services other modules publish.

The Sequence repositories hold the only raw SQL in Essential, a deliberate exception to the engine-first rule (docs/wiki/07 §6.7): issuing a number needs INSERT ...

Package currency declares the currency capability that Essential offers to other modules.

Package module declares the layers of the essential_module_metadata resource: one row per module the binary has ever loaded, kept in step with the loader by SyncModuleMetadata at boot.

Package timezone declares the search over the hardcoded timezone catalogue.

Package uom declares the UoM capability that Essential offers to other modules.

Package uomcat declares the UoM Category resource's layers.

Package settings holds iam's settings schemas.

Package dynamicengines declares the resource onions the IAM module serves through the composable resource engine, and registers them into the dependency container during the module's Init().

Package itstorage owns every uploaded file: the storage space tree, the file records, and the objects in S3.

Package dynamicengines declares the resource onions IT Storage serves through the composable resource engine, and registers them and their typed layers into the dependency container.

Package external binds IT Storage's local ports to the services other modules publish.

Package consumption declares the layers of the itstorage_consumption resource: the bytes each tenant, organization and user stores, and the bytes reserved by uploads still in flight.

Package external declares the ports IT Storage holds onto other modules.

Package file declares the layers of the itstorage_file resource: one stored object and its metadata.

Package space declares the layers of the itstorage_space resource: the system-managed tree that files are stored in.

Package transport subscribes IT Storage to the org lifecycle commands and mounts its routes.

Package jobscheduler runs recurring jobs registered by other modules.

Package services holds the scheduling engine and the rules it applies.

This file contains the only raw SQL in the Job Scheduler, and it is a deliberate exception to the engine-first rule in docs/wiki/07 §6.7 rather than drift.

Package settings holds Notification's settings schemas.

Package dynamicengines declares the resource onions the Notification module serves through the composable resource engine, and registers them into the dependency container during the module's Init().

Package external binds Notification to the infrastructure and to other modules.

Package channels holds the distribution channels themselves.

Package delivery declares the contracts for raising and reading notifications.

Package cqrs receives the commands other modules dispatch into Notification.

Package paymentinvoice takes payments through the payment gateways the business has contracts with, and issues the invoices that account for them.

Package app holds the Payment & Invoice application services.

Package services holds the rules of the Payment & Invoice module: what may be paid, what may be refunded, and what state an order is left in when a gateway answers.

Package settings holds Payment & Invoice's settings schemas.

Package dynamicengines registers the composable onions of the Payment & Invoice resources and publishes their typed layers into the dependency container.

Package external binds Payment & Invoice's local ports to the services other modules publish.

Package event publishes this module's announcements on the internal Watermill bus.

Package gateway builds the gateway registry this deployment will actually serve payments through, from configuration.

Package momo talks to MoMo, a Vietnamese e-wallet.

Package mpos talks to mPOS (NextPay), which drives a physical card terminal.

Package vietqr talks to VietQR, which settles bank transfers made by scanning a QR code.

Package event is what this module announces to the rest of the build when an order reaches a verdict.

Package gateway declares what a payment gateway must be able to do, and nothing about how any particular one does it.

Package invoice is the Payment & Invoice module's port for raising a fiscal document on behalf of another module.

Package order is the Payment & Invoice module's port for taking money and giving it back.

Package paymentmethod is the port through which another module reads this one's payment method master data.

Package paymentprofile declares the CRUD layers of the paymentprofile resource.

Package transaction declares the CRUD layers of the transaction resource.

Package v1 serves the gateway callbacks.

Package settings gives every feature module one place to declare its configuration and have it stored, resolved and rendered, instead of each building its own settings table.

Package dynamicengines declares the resource onions the Settings module serves through the composable resource engine, and registers them into the dependency container during the module's Init().

Package settings declares the capabilities the Settings module exposes to the rest of the application: schema registration, and the per-level read and write of setting values.

Package settingsquota declares the layers of the settings_quota resource: how much of a named resource one tenant, organization or user may use.

Package settingsrecord declares the layers of the settings_record resource: one stored value per module, setting name and owner.

Package settingsschema declares the layers of the settings_schema resource: one row per module and level, holding the setting definitions a module registered at boot.

Package transport subscribes Settings to the org lifecycle commands.