CloudWinks · Foundation apps

GoldenRuleTechnical brief

GoldenRule is where CloudWinks keeps its business rules. Apps ask it for a decision and get an answer back, so the same policy is applied the same way in every app.

Read the business brief · PDF

1. Architecture in brief

GoldenRule is a Foundation app with company ownership and the gold_ prefix. Evaluation is server-side in SQL. One rule model covers three kinds: CONDITION, RULE_SET and DECISION_TABLE, with hit policies FIRST, UNIQUE and COLLECT and a JSON condition grammar. Published versions are immutable, and every execution records the version it used. Rules return decisions only and have no side effects.

2. Service boundary and intake

Apps, TheBoss and WorkerBee call evaluation by rule key with the calling person’s identity, which is required and never defaulted. A jurisdiction key (an ISO 3166-1 country plus an optional ISO 3166-2 subdivision) selects the most specific matching rule. Rule sets include zibit.lending.caps (cap values come from legal review; an unset cap means block), zibit.lending.limits, landman.comparable.adjustment_caps, dreamdrafter.plan.checks and payroll.controls. Timed checks are Conductor schedules owned by the acting app.

3. Data handled

The model holds rules, rule sets, decision tables, versions, tests and an execution log. The log keeps the version, the outcome, the outputs, what matched and an input hash, under a retention policy. Company-owned rules sit beside CloudWinks templates that are readable by all; person-owned processes use inline conditions only.

4. Integrations and ownership

TheBoss and WorkerBee evaluate routing and branch decisions. Zibit, LandMan, DreamDrafter and TjingTjing call their named rule sets. WatchDog can use rules for requirement checks. Conductor runs timed checks for the owning app. Crux supplies identity and ISO jurisdiction codes.

5. Security and access

A decision needs both a service grant to the calling app and the person’s own rights; the narrower wins. Nothing is granted to PUBLIC, the calling user is never defaulted to an owner, and there is no developer fallback user. Rules carry no outside webhook bindings.

Competitive context

AlternativeIts focusCloudWinks product focus
DroolsA rules engine with rule sets and spreadsheet decision tables.Decision-only rules with fixed versions, shared by CloudWinks processes, agents and apps.
Microsoft Dataverse business rulesForm and data rules that validate fields and guide a process.One server-side rule service with jurisdiction keys and a full decision log.

Read the business brief →

← More Foundation apps apps · All application briefs · How the framework works