The approval chain
A request moves through people. Guards decide who may move it and when: a total above a threshold needs a second signature, a group name is a formula. Field rights per state freeze the amount once it is approved.
Anything with a state is a document. FadoDB is a state-aware workflow engine that is also the database. The things it holds are not only forms that wait for a signature. An invoice has a state. So does a purchase order, a contract, a supplier, an employee's leave balance, a permit, a work order, a loan, a claim, a field in a farm, a period in the general ledger. Each of them is one declarative class: typed fields, Excel-style formulas, a statechart, rules that fire on a change, and access as a formula. The engine computes it, refuses what does not hold, records every change with who and when, and answers in SQL.
Every case below can run without a screen. The agent is the interface: it drafts the class, previews each change and commits on behalf of the person it serves. FadoDB is the system: it computes, refuses, remembers and answers, and the guards hold whoever is asking. The samples come from every corner of an enterprise we could think of. Each card says what the document is, what the formulas compute, what the states are, and which transitions need a guard.
Find the shape, and the class almost writes itself. An agent can draft it in one call; the engine tells it where the draft does not hold.
A request moves through people. Guards decide who may move it and when: a total above a threshold needs a second signature, a group name is a formula. Field rights per state freeze the amount once it is approved.
A thing that exists for years and changes state rarely: an asset, a contract, a supplier, a licence, an employee. Dates are formulas; a scheduled formula flags what expires next month. The history table is the register's memory.
Entries that must balance, inside periods that close. A guard refuses an unbalanced entry; a terminal state freezes a closed period and everything posted in it. A reversal is a new document, never an edit.
Two or three records that should agree: order, receipt and invoice; bank line and book entry; count and stock. A formula computes the difference, a guard accepts it inside a tolerance, and the unmatched rest becomes a case.
Something happened and someone must answer by a deadline: a complaint, an incident, a data subject request, a tender question. The deadline is a formula over the business date, a scheduled rule escalates, and the log proves when each step happened.
One agreement, many dated amounts: a lease, a loan, a grant, a subscription, a deposit plan. The rows are the schedule, each row's state tells what is due, paid or waived, and the totals are formulas over the rows.
Finance is where FadoDB's exact decimals and its append-only history earn their keep. Rounding is written in the formula, a closed period is a terminal state, and every number can be traced to the commit that set it.
The invoice as a document: lines, net, tax rate from a table, gross as a formula. Approval above a threshold needs a second group; the amount is read-only once approved.
Receipt rows with category, amount and currency, converted at the business date's rate. Policy limits are guards. Card statement lines are matched to receipts, and what is left becomes a query.
A journal as a Fado class: rows of account, debit and credit; a guard refuses posting unless the sums agree. A reversal is a new entry that points back. The ledger is a SQL view over the posted ones.
One document per period with a checklist of rows, each owned and ticked. Hard close is a terminal state; a rule refuses any posting with a business date inside a locked period.
Shared costs spread over cost centres by driver tables: headcount, floor space, revenue. The run computes every share as a formula, is previewed before it is booked, and each version of the keys is kept.
Mutual balances between group entities as rows, netted by a formula, agreed by both sides through two guarded transitions, then settled. Differences open a reconciliation case.
A cost centre's budget as rows per line and month, totals as formulas, variance against last year from a lookup. Each resubmission is a new version; the approved one is frozen and compared against actuals in SQL.
Order, goods receipt and invoice meet in one document. Quantity and price differences are formulas; a guard lets the match pass inside a tolerance table, and the rest waits for a person.
Issued against an invoice, never above its remaining balance, which is a lookup. Approval depends on the reason code and the amount. Issuing it creates the payment document through a rule.
One document per asset with cost, useful life and method. Depreciation to date is a formula over the business date; impairment and disposal are transitions that freeze the book value they produce.
Cash flow rows, with payback and net present value as formulas. The approval route is a guard on the total: the plant manager, then the CFO, then the board above the top band.
Thirteen weeks of inflows and outflows as rows, closing balance as a running formula. Every weekly update is a version, so forecast accuracy is a query that compares versions with what happened.
Each statement line is a document matched to a book entry by amount, date and reference. Unmatched lines age by a scheduled formula and escalate; the explained ones carry their reason into the audit trail.
The return computes its boxes from the posted invoices of the period with a query, is checked against the ledger by a formula, and is frozen when filed. A correction is a new return that references the old one.
One agreement, a row per period with the amount to recognise. A rule posts the row that falls due when the period opens, and the remaining balance is a formula over the rows still open.
Payments as rows, the discount rate from a table, the liability and the right-of-use asset as formulas. A modification is a transition that recomputes from its business date and keeps the old schedule in history.
Days overdue is a scheduled formula on the invoice. Each reminder level is a state with its own letter and fee from a table, and a rule moves the invoice up a level when the grace period runs out.
A contract with its performance obligations as rows: allocated price, method, progress. Recognised revenue per period is a formula, and the deferred balance follows. Each change to the contract is a version an auditor can read.
A float per office with voucher rows. The cash on hand is a formula; replenishment is a transition that only the holder's manager may make, and the count at hand-over is a snapshot.
The run is a document; gross, deductions and employer cost are formulas over the employee rows and rate tables. Four eyes approve it, the payment file is created by a rule, and the amounts are frozen on pay-out.
A payment batch whose release needs two different principals, each a guard. Limits per approver live in a table, the second approval may not be the first approver, and the release calls the bank through the outbox.
An award with a budget per cost category, eligible spend as rows, and the claimable amount as a formula under the funder's rules. Each reporting period is a transition that freezes what was claimed.
One document per intercompany arrangement: the method, the benchmark range from a table, the actual margin as a formula over the year's postings. Out of range is a flag that opens an adjustment.
Adding or retiring an account is a request with a reason, an effective date and an owner. Retirement is guarded by a lookup that the account's balance is zero. The chart itself is a table the journal validates against.
Requisitions, tenders, orders, receipts and returns are documents that reference each other. A formula on one can look up another, and a rule on one can create the next.
The supplier record is a document with its bank details, certificates as attachments and a screening result. Activation needs procurement and finance; suspension freezes every open order through a rule.
Bids as rows with price, lead time and quality score; the weighted total is a formula from a criteria table. Opening the bids is a transition only the committee may make, and the award is a snapshot.
What is needed, by when and against which budget line. A lookup checks the remaining budget, the approver is a formula over the amount and the cost centre, and approval creates the purchase order.
Lines with quantity, price and expected date; total and open quantity are formulas over lines and receipts. Confirmation by the supplier, partial receipts, and closure when everything is received or cancelled.
The notice date is a formula from the end date and the notice period. A scheduled formula flags contracts entering their notice window, a rule opens a renewal review, and the decision is recorded before the deadline.
What arrived against what was ordered, with inspection rows and a sampling rule from a table. Acceptance posts stock; rejection creates a return and a supplier complaint through rules.
Count rows against book quantity, variance and its value as formulas. Recounts are new versions; posting the adjustment is guarded by a tolerance and by a second person above it.
A quarterly document per supplier: on-time rate, defect rate and responsiveness from queries over receipts and complaints, weighted into a score. Below a floor, a rule opens an improvement plan.
A customer's return referenced to the original order line, with a reason, a photo and the refund amount as a formula under the return policy table. Receipt of the goods unlocks the refund.
A shipment with its packages as rows and the carrier's updates as events. Expected arrival is a formula; a scheduled rule marks it late and notifies the buyer, and proof of delivery closes it.
Lines with tariff codes from a table, duties and taxes as formulas on the declared value. Lodging freezes the lines; clearance and release are recorded with their timestamps for the audit.
Lines leave one location and arrive at another. In transit is a state, the quantity difference on arrival is a formula, and a difference beyond tolerance opens a discrepancy case automatically.
Sales, marketing and operations each submit a row of numbers per product and month; the consensus is a formula they agree on. Every cycle is a version, so bias per team is a query over history.
Opened from a failed match with the disputed lines and the expected values. The supplier's answer is a transition, the settlement is a credit note or a corrected invoice created by a rule, and the case closes.
A product or service as a document: codes, units, suppliers and prices with effective dates. Introduction and discontinuation are transitions; a discontinued item cannot be ordered, which is a guard elsewhere.
Quotes, orders, subscriptions and complaints are the processes a customer actually feels. Each one is a document whose totals are formulas and whose promises are states with dates.
Lines, discounts, taxes and shipping as formulas with exact money. Confirmation checks credit through a lookup, picking and shipping are states with their timestamps, and the invoice is created by a rule.
Configured lines with list prices from a table and a discount per line. Margin is a formula; a discount beyond the rep's limit needs the sales director, which is a guard. Acceptance creates the order.
Stages as states, probability from a table per stage, weighted value as a formula. Time in stage is a query over the event log, so the pipeline report and the forecast come from the same documents.
Plan, seats and price from a table, monthly value as a formula. Trial ends by a scheduled rule, a failed payment moves it to past due, and cancellation is a terminal state the report counts as churn.
A new account with its contacts, tax numbers and requested credit limit. The granted limit is guarded by a rating lookup; activation needs finance, and the record becomes the master the order checks.
A case with a severity from a table and a due date as a formula. A scheduled rule escalates when the deadline passes; resolution needs the customer's confirmation or a timeout, both transitions.
Whether the product is in warranty is a formula over the purchase date and the warranty table. The decision is repair, replace or refund, each a transition that creates the next document.
Points earned and spent as rows with their dates. The balance and the tier are formulas; points expire by a scheduled rule after a year, and every change is in the history the customer may read.
A new price list is a document with its rows and an effective date, approved before it goes live. The live list is the approved version with the latest effective date, which is what the quote looks up.
Computed for a rep and a period from the won deals by a query, with rates and accelerators from the plan table. Disputes are a transition back; payment freezes the statement.
Tiers as rows: a threshold and a rate. Purchases to date come from a query, the earned rebate is a formula over the tiers, and the accrual is posted monthly by a rule until the agreement is settled.
Stock placed at a customer stays the supplier's until consumed. Consumption reports are rows; what to invoice is a formula, and the invoice is created by a rule at the end of each period.
A promotion with its funding, dates and expected lift; actual spend arrives as retailer deductions matched against it. The open commitment is a formula, and closing it reconciles what the retailer took.
Exposure is a query over open invoices and orders; the limit and the rating are fields. Over the limit, a rule blocks new orders by changing the customer's state, and the review documents who lifted the block.
HR processes mix arithmetic with confidentiality: a leave balance, a salary band, a grievance. Access as a formula keeps the salary to the manager and HR, on the server and in every query.
A role, a grade, a budget line and a start date. Approval checks the headcount plan through a lookup; approval posts the job and the requisition closes when the offer is accepted.
Each application is a document with its interviews as rows and scores as formulas. The salary expectation is readable only by HR and the hiring manager. Rejection sends the letter through the outbox.
A checklist of rows, each with an owner and a due date relative to the start date. Readiness is a formula over the rows; the IT access request and the equipment order are created by rules.
Days requested is a formula over the calendar table; the balance comes from a lookup over this year's approved requests. A guard refuses more than the balance, and the manager approves.
A week of hours as rows per project and day. Overtime is a formula from the contract table, approval is the project lead's, and the billable rows feed the client invoice through a query.
Objectives as rows with a weight and a rating; the overall rating is a formula. The self review is hidden from the manager until submitted, and the final rating is frozen after calibration.
The new salary against the band from a grade table; the position in band and the increase are formulas. Beyond the band or the budget, a guard asks for the head of HR. Only the chain of approvers can read it.
One document per person and certificate with the date obtained and the validity. Expiring soon is a scheduled formula, a rule books the refresher, and an expired certificate blocks assignments elsewhere.
The leaver's checklist: access to revoke, assets to return, final pay to compute. Completion is a formula over the rows; the last day is a scheduled transition that revokes access through a rule.
A confidential case whose access rule names the investigator, the HR partner and nobody else. Statutory steps are states with deadlines; the outcome letter is an attachment on the closing transition.
Destination, dates and purpose; the per diem is a formula from the destination table and the number of days. Approval depends on the estimated cost, and the approved trip becomes the expense report's parent.
Positions as rows with grade, start month and cost from the band table. The annual cost is a formula, the plan is versioned per budget round, and the hiring requisition checks it by lookup.
The person's master document: contract, grade, manager and location, with every change a version with its effective date. Who may read which field is a formula per field, and the org chart is a query.
A contractor's engagement with its rate, cap and end date. Spend to date is a query over approved timesheets, a guard refuses extension past the cap, and the end date triggers access removal.
Regulators ask two questions: did you do it in time, and who did it. In FadoDB the deadline is computed from the business date, and every step is an event with a principal and a timestamp.
The agreement with its parties, value, term and the signed copy as an attachment. Legal review is guarded by the value and the template deviations; the term end feeds the renewal process.
The fast track: a standard template needs no lawyer and a changed one does, which is a guard on a flag. The counterparty, the term and the signed file are the fields; expiry is a scheduled state change.
Document management as a class: the file, the owner, the review cycle and the acknowledgements as rows. A new version starts a review; publication retires the old one, and the next review date is a formula.
Likelihood and impact from scales in a table, the score as a formula, the owner and the mitigations as rows. Acceptance above a score needs the risk committee, and the heat map is a query.
A finding with its severity, the action plan as rows with owners and dates, and overdue actions as a scheduled formula. Closure needs the auditor's verification, a guard only the audit group passes.
The notification deadline is a formula, seventy-two hours from awareness. Severity decides whether the authority and the subjects must be told; the hours left are on the document and a rule escalates at twenty-four.
The statutory month is a formula over the receipt date, extendable once with a reason. Identity verification is a guard before any data is gathered, and the response pack is an attachment on the closing step.
An annual declaration per employee with interests as rows. A rule creates the declarations each January; the undeclared are a query, and a declared conflict opens a review with a mitigation decision.
What was received or given, from whom and its value. Under the threshold it is recorded; over it, a guard asks the compliance officer. The yearly total per counterparty is a formula over the register.
The strictest access rule on the site: the case is readable by the named investigators only, and the reporter's identity is a field that even they may not see. Acknowledgement and feedback deadlines are formulas under the directive.
A possible match between a counterparty and a list entry, with the score and the matched fields. A true match freezes the counterparty through a rule; a false positive is recorded with the reviewer's name.
The motion, the votes as rows, and quorum and majority as formulas over the directors table. Adoption is a transition that passes only when the formulas hold, and the adopted text is frozen.
Who may sign what, up to which amount, until when. The register is a table other classes read in their guards, and each change to it is itself a document with an approval chain.
Every licence the company holds, with its authority, conditions and expiry. The renewal lead time is per type from a table, the renewal case is created by a scheduled rule, and the lapse is a state nobody wants to see.
The loss, the policy from a table, the deductible and the expected recovery as formulas. Submission to the insurer, their offer and the settlement are transitions; the gap between loss and recovery is a query.
A matter with its counsel, exposure, probability and the provision as a formula the finance team posts. Court dates are rows; the hearing next week is a scheduled flag, and the outcome freezes the file.
One document per obligation and period, created by a rule from a table of obligations. Days to the deadline is a scheduled formula; the evidence is attached on filing, and the late ones are a query the board sees.
What a person agreed to, when, through which text version, and when they withdrew. The current consent is the latest version; proof for an audit is the history row with its timestamp.
The IT department runs on state machines already. Here they are declared instead of coded, and the same log that approves a change also answers the auditor's access review.
Risk and impact from tables give a change class as a formula; a standard change skips the board and a major one does not, which is a guard. The implementation window is a date range the rule enforces.
Priority is a formula over impact and urgency from a matrix table; the response and resolution targets follow from the priority. A scheduled rule marks the breach, and time to resolve is a query over the events.
Who asked for which entitlement, who approved, when it was provisioned and when it must be reviewed. The quarterly recertification is a rule; an unconfirmed access is revoked by another one.
A laptop from order to recycling, with its assignee, its warranty end and its repairs as rows. The remaining warranty is a formula; retirement is guarded by a wiped-disk attestation.
The licence as a document with its seat count; assignments as rows. Seats used and seats free are formulas, over-allocation is refused by a guard, and the true-up is a query the vendor cannot argue with.
The release with its tickets as rows, the test evidence as attachments and the sign-offs as guarded transitions. Deploying calls the pipeline through the outbox and records the result as an event.
Each test is a document with the systems as rows, the measured recovery time and the target from a table; met or missed is a formula. The tests due this quarter are created by a rule.
A parameter change as a document: the key, the old value from a lookup, the new value and the rollback plan. Production needs a second person; applying it writes the configuration table through an action.
Every run is a document: inputs, row counts, duration as a formula, result as a state. Failures retry through the outbox a configured number of times, and the success rate per pipeline is a query.
Every certificate with its hosts, issuer and expiry. Days left is a scheduled formula, the renewal task is created at thirty days by a rule, and the owner who ignored it is in the log.
A request from a catalogue table that gives the approver, the fulfilment group and the target time. The form fields are the class's variables; the fulfilment steps are rows ticked by the group.
Linked incidents as rows from a query, the root cause, the workaround and the permanent fix as a change request created by a rule. The problem closes when the change is verified, a guard over the lookup.
An AI SOC needs one record of each case: what the agent found, how sure it is, what was done, who did it and what is allowed next. In FadoDB that record is a document. The agent reasons; the access formula on each transition decides what it may do alone and what waits for a person. How an AI SOC runs on FadoDB.
Every alert from the SIEM or the EDR is a document. The agent writes its verdict, its confidence and the evidence as rows; severity is a formula over the alert score and the asset's tier from a table, never the model's guess. Dismissing an alert alone takes high confidence and a severity below critical.
The playbook is the statechart: containment, eradication and recovery are states, and each step's evidence is rows. Containing a workstation is the agent's to do; containing a production server needs the on-call analyst, an access formula on the transition.
The agent isolates a host and the document starts a review window. The on-call analyst confirms or releases it; if nobody answers, the case escalates. Release is a transition, so the log says who undid what the agent did, and why.
An employee reports an email; the agent extracts the sender, the links and the attachments as rows and scores them. A confirmed phish is pulled from every mailbox through an action, and the reporter hears the outcome when the case closes.
Impossible travel or a burst of MFA prompts opens a case on the identity. Revoking the sessions and forcing a reset are actions on the containment step; an executive's account needs a second person, a guard over the role from the directory table.
Each finding carries the CVE, its CVSS score and the asset's tier; the due date is a formula over both, shorter when the CVE is known to be exploited. Overdue without an approved exception is a query the CISO reads on Monday.
Who accepted which risk, with which compensating controls, until when. The approver's level is a formula over the residual risk, and when the exception expires the finding it covered opens again.
An address, a domain or a file hash with its source, its confidence and its expiry. Indicators above the bar are pushed to the blocklists by an action and withdrawn when they age out, so the list does not grow forever.
A new or tuned detection as a document, its test results as rows and its false-positive rate as a formula. Going to production is guarded by the tests, and a detection that floods the queue is rolled back by a transition anyone on call may take.
Each finding from the report with its severity, the asset and the owner. Closing it needs the retest evidence attached, a guard; the open findings by severity and age are the next test's scope, as a query.
Emergency administrator access as a document: who, which system, why and for how long. The grant ends by a timer no session may outlive, and someone other than the holder must review it before the case closes.
Every change an AI agent made is an event with its principal, so the unusual ones are a query: a new system, a burst, a transition it never took before. Each flagged action becomes a review case for a person, and narrowing what the agent may do is one formula.
The questionnaire answers as rows, weighted into a score by a formula from the question table. A score under the bar needs a risk acceptance; the next assessment date is a formula over the tier.
Who holds which credential for which system, issued when, rotated when. Rotation due is a scheduled formula; a leaver's credentials are revoked by the offboarding rule, and the log shows every rotation.
Quality systems demand that nothing is edited after the fact. FadoDB's history is append-only by construction, so the batch record you show the inspector is the one that was written.
Materials and operations as rows with planned and actual quantities; yield and cost are formulas. Release is guarded by material availability from a lookup, and completion posts the finished goods.
The deviation, its containment, the root cause and the corrective actions as rows with owners. Verification needs quality assurance, a guard, and the effectiveness check is a scheduled transition months later.
The affected parts and drawings as rows, the cost impact as a formula, the effectivity date as a field. Approval by engineering, quality and production are three guarded transitions, in any order the class allows.
The batch with its inputs as rows, each a reference to a supplier lot, and its process parameters with limits from a table. Out of limit is a formula that blocks release; the genealogy is a query across batches.
Each asset's maintenance plan as rows with an interval in days or in meter units. The next due date is a formula over the last reading; a rule creates the work order when it comes, and the parts used are rows.
An instrument's calibration with the readings as rows and the deviation as a formula against the tolerance. Out of tolerance opens an impact review on everything measured since; the certificate is an attachment.
What happened, to whom, with a severity from a table that decides whether the authority must be told and by when, a formula. The investigation steps are states, and the actions are rows with owners.
A permit valid from an hour to an hour, with the isolations as rows and the gas test as a field. Issue and acceptance are two different people, a guard; expiry is a scheduled transition that no work may outlive.
Components as rows with quantities and unit costs from the item table; the rolled-up cost is a formula. A revision is a new version with an effective date, and the one in production is frozen.
The supplier's sample with the measured dimensions as rows against the drawing's tolerances from a table. Pass or fail per row and overall are formulas; approval is quality's transition.
Dispatched to a technician with a time window; arrival and completion are transitions with timestamps. Parts and hours are rows, the price is a formula from the contract table, and the invoice follows by a rule.
A non-conforming lot waits for a decision: use as is, rework, scrap or return. The cost of each option is a formula; the decision is a guarded transition by the review board, and the chosen path creates its order.
A document per shift with the open issues as rows carried over from the previous shift by a rule. Acceptance by the incoming lead is a transition; the issues that survived five shifts are a query.
A daily or weekly checklist of rows with expected ranges from a table. A reading outside its range is a formula that creates a maintenance request through a rule, and the round is signed by the inspector.
The lease with its rent, indexation clause and break dates. The indexed rent is a formula over a published index table, the next indexation is a scheduled rule, and the break notice is a deadline formula.
A request against a unit, with the category deciding the response target from a table. Assignment to a contractor is a transition, the cost is a field only the owner may read, and closure needs the tenant.
Work done to date per item as rows against the contract sum; the certified amount, the retention and the payment due are formulas. Certification is the engineer's transition, and each claim references the last.
Defects as rows with a location, a photo, a responsible contractor and a due date. Open items is a formula; handover is guarded by zero open items of the blocking kind.
Readings as rows per meter and date; consumption and the charge are formulas from the tariff table. The recharge to each tenant is created by a rule at the end of the period.
A booking for a resource and a time range; a guard refuses an overlap found by a lookup. No-show after fifteen minutes is a scheduled transition that frees the resource, and occupancy is a query.
The application with its drawings, the fee as a formula over the floor area and the fee table, and the statutory decision deadline as a formula. Conditions are rows the construction must discharge.
Budget, commitments and spend per cost code as rows from queries over orders and invoices; forecast at completion is a formula. A variation beyond the contingency needs the sponsor.
A loan, a claim, a referral, a grant, a grid connection and a crop record are the same shapes with other field names. The industry's rules go into tables and guards; the engine does not change.
Referred by one clinician to another with an urgency that sets the target wait from a table. Days waiting is a scheduled formula, breaches are a query, and access is limited to the care team by formula.
A treatment request to a payer with the codes, the clinical justification and the decision deadline as a formula. Approval, denial and appeal are states; the approved units are a field the claim later checks.
A subject's visits as rows with windows computed from the enrolment date and the protocol table. A visit outside its window is a formula that creates a protocol deviation through a rule.
A complaint whose reportability to the regulator is a formula over the severity and the outcome, with the statutory deadline that follows. The investigation and the report are states with evidence attached.
A prescription with its lines, interactions checked by a lookup, and a controlled substance that needs the pharmacist's second check, a guard. Dispensing posts stock and the record is frozen.
Income, debts and the requested amount; the debt-to-income and loan-to-value ratios are formulas against limits from a product table. Underwriting approves within its authority, a guard; disbursement calls the core system.
Risk factors from tables, the premium as a formula, the endorsements as versions. Renewal is a scheduled rule that creates the renewal quote; non-payment lapses the policy after the grace period.
First notice, the coverage check as a lookup on the policy, the reserve as a field only the adjuster sets, the payment as a formula under the deductible. Settlement above the adjuster's authority escalates.
Our record of a trade and the counterparty's do not agree. The differences are formulas per field, the age of the break is a scheduled formula, and resolution records which side corrected what.
Identity documents as attachments, the risk rating as a formula over country, product and screening result. Enhanced due diligence is a state the rating sends the case to; activation is compliance's transition.
A dispute with its reason code, the deadlines for each stage from the scheme's table as formulas, and the evidence as attachments. Missing a deadline is a scheduled transition that loses the case.
Exposure and collateral as fields updated daily, the call amount as a formula over the threshold and the minimum transfer. A rule issues the call; delivery or dispute by the deadline are transitions.
A citizen's application with the fee as a formula and the statutory decision time as a deadline. Silence past the deadline may be a deemed decision, which is a scheduled transition the class can model.
The funder's side: applications scored by rows of criteria, the ranking a query, the award a transition with a budget. Reporting milestones are rows that a scheduled rule chases.
Bids opened at a time, scored by a committee, and a standstill period before the contract, computed from the notice date. Every step is in the log with its principal, which is what a challenge will ask for.
The statutory response time is a formula, extendable under named exemptions. The released documents and the redaction reasons are attached; the late responses are a query the oversight body sees.
A student's registration for a course, with prerequisites checked by a lookup over completed courses, a guard. Credits this term is a formula with a maximum; the wait list is a state with a rule that admits.
Eligibility is a formula over income, grades and the programme's table; the award amount follows. Disbursement per term is a row, and a dropped course below full time suspends the award through a rule.
Submission, the examiners as rows, their verdicts and the final grade as a formula. The defence date is set by a transition only the faculty office may make, and the approved thesis is frozen.
A pledge with its instalments as rows; received and outstanding are formulas. A missed instalment is a scheduled state change with a gentle reminder through the outbox; the thank-you letter is a rule.
Requested capacity, the study fee as a formula, the offer with its validity as a deadline. Acceptance is a transition that commits works; energisation closes it, and the queue is a query over open requests.
Customers affected from a lookup, the regulatory reporting threshold as a formula, restoration time as a timestamp difference. Compensation due per customer is a formula the rule turns into credits.
A bill per customer and period: the reading, estimated or actual, the consumption and the charge as formulas over a tariff table with time bands. The estimated bill is corrected by the next actual reading, a new version.
A port between operators with the regulated deadline as a formula from the request date. Validation, the donor's answer and the switch are states; a rejection must carry a reason code from a table.
Activity data as rows, emission factors from a versioned table, tonnes as formulas. Each reporting period is a document frozen on submission; a factor update is a new table version, never a rewrite.
Legs as rows, the rate from a carrier table by lane and weight band, surcharges as formulas. The quote's validity is a deadline; the booking is a transition that references the quote version accepted.
A shortage or damage against a delivery, with the proof of delivery attached and the claim value as a formula over the lines. The carrier's liability limit comes from a table; the claim deadline is a formula.
Stock, minimum and maximum per item as rows with the order quantity as a formula. A rule creates the order each night; above a value threshold the store manager confirms, a guard.
The items, the current and the proposed price, the margin after markdown as a formula. Deeper than the category's limit from a table needs the merchandising director; the new price is effective by rule.
Guests, menu and rooms as rows, the total as a formula, the deposit schedule as rows with due dates. A missed deposit is a scheduled state change; the final count locks seven days before.
A room block with a cut-off date and an attrition clause. Rooms picked up come from a lookup, the attrition charge is a formula, and the cut-off releases the unsold rooms through a rule.
Milestones as rows with their fees and acceptance states; burn against budget is a formula over approved timesheets. A milestone accepted by the client, a transition, creates its invoice.
What changes, what it costs and what it does to the schedule; the new contract value is a formula. The client's approval is a transition only their principal may make, and the engagement is updated by a rule.
A piece from pitch to publication, with the legal review a state the class requires only for flagged topics, a guard. The embargo is a scheduled transition; every edit is a version with its author.
Reported sales as rows, the rate per channel and tier from the contract table, the royalty as a formula, the advance recouped as a running balance. The statement is frozen when sent and disputable by transition.
Placements as rows with the booked and delivered volumes; under-delivery and the make-good are formulas. The campaign's end is a scheduled transition that creates the reconciliation and the invoice.
Unbilled time and expenses from a query per matter, the proposed invoice with write-offs as fields, realisation as a formula. The partner approves the write-off above a percentage, a guard.
A field for a season: the crop, the applications of fertiliser and plant protection as rows, with the maximum dose and the pre-harvest interval from a product table. Harvest is guarded by the interval having passed.
Animals as rows with their identifiers, the origin, the destination and the notification deadline as a formula. Standstill after arrival is a scheduled state; the herd's history is a query across movements.
A vehicle with its driver, mileage readings as rows, and the next inspection and insurance renewal as formulas. A rule books the inspection; an expired inspection takes the vehicle off the road, a state.
A vessel's call with its services as rows, the port dues as formulas over tonnage and the tariff table, and the agent's disbursement account as the total. Berthing and sailing are transitions with their times.
Some uses are not a business process but a way of running one: an agent's own work, a sandbox, a reference table with history, or a state machine your application needed anyway. How FadoDB governs agents.
An agent proposes, a person disposes. Each proposed action is a document the agent creates and may not approve, a guard on the principal's group. The person's decision is a transition; the agent reads it and acts.
Every task an agent takes on is a document with its inputs, its attempts as rows and its result. Retries, timeouts and hand-offs to a human are transitions, so what the agents did last night is a query.
Copy the class into a scratch file, replay a hypothetical sequence of transitions, and query the result. Cheap single files mean an agent can run one sandbox per experiment and keep only the class that worked.
Cycle time per state, rework loops, who approves slowest: all are SQL over the event log that every class writes anyway. No export, no second system, and the mined class can be redrafted and previewed.
Exchange rates, tax rates, price lists and calendars as tables, each change a documented request with an effective date. Formulas look them up as of the business date, so last year's invoice recomputes the same.
A multi-step operation across services as one document: each step a state, each call an outbox action with retries, each failure a compensating transition. The log is the saga's history.
Each page of a wizard is a state and its fields are the variables writable in that state. Validation is the class's own; the browser VM shows the computed values live, and an abandoned draft resumes where it stopped.
The delegation of authority as one table: document type, amount band, required group. Every class's approve transition reads it in its guard, so changing the matrix changes every process at once, with history.
A feature's rollout as a document: the cohorts as rows with their percentages and dates, the kill switch as a transition anyone on call may make. Your application reads the current state through the API.
One file, pure Go, no server: a point of sale, a field inspection app, a lab instrument's records. The same class runs offline and the event log is what you ship to the centre when the connection returns.
Every company has a workbook that runs a process: a tracker with a status column and formulas. Its formulas already speak FadoDB's dialect. The status column becomes a statechart, and the versions nobody kept become history.
Each control as a document with its evidence requests as rows, due dates from the audit calendar, and the collected files attached. Coverage is a formula; the auditor reads the history, not a screenshot.
Nothing matches that search. Try a broader word, such as approval, deadline, register or schedule.
A class is one JSON document. Start from the Invoice on the front page, rename the states, write the formulas you already know from the spreadsheet, and store the first document today.