@geonosis/policy 1.0.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,107 @@
+# `@geonosis/policy`
+
+A threshold is not a number. It is a number, plus the authority that set it, the subject it reaches
+and the reason it exists — and that difference is what lets the person who was just blocked learn
+something instead of filing a ticket.
+
+This is the kernel two repos arrived at independently: a precedence lattice with a full trace, a read
+that resolves **authored rule → config row → the caller's own constant** and RECORDS the third case,
+the learning loop that reads those recordings back, and a permission lattice with the runtime lifted
+out of it.
+
+```ts
+import { definePolicy, readPolicy } from '@geonosis/policy'
+
+const policy = definePolicy({
+  tiers: [
+    'regulatory',
+    'contract',
+    { name: 'tenant', overridable: true },
+    { name: 'command', overrides: true },
+    { name: 'learned', advisory: true },
+  ],
+  kinds: [{ kind: 'quoteExpiryDays', schema: z.number().positive() }],
+  scopeKeys: ['region', 'customerGroup', 'companyId', 'orderId'], // VAGUEST first
+})
+
+const { value, usedFallback } = await readPolicy(policy, 'quoteExpiryDays', { companyId }, {
+  fallback: DEFAULT_QUOTE_EXPIRY_DAYS,
+  rule,
+  config,
+  journal,
+  op: 'create-quote',
+})
+```
+
+**The kernel is inert until the data arrives.** Not one tier, kind, scope key or rule is built in: the
+two consumers disagreed on every one of them — one's strongest authority is `regulatory`, the other's
+is `physics`, and they share not a single scope key — so all four are declared. A policy with no
+rules decides nothing, every read falls through to the caller's constant, and each of those is
+recorded exactly **once per boot**: the honest unit of evidence for "nobody has set this knob" is a
+deployment, not a request, and a constraint read once per cart would otherwise write a row per cart
+and drown the one signal anybody is looking for.
+
+## What is in it
+
+| Export | What it does |
+|---|---|
+| `definePolicy({ tiers, kinds, scopeKeys, rules })` | The lattice as data. Refuses two escape hatches, a duplicate tier or kind, and an advisory tier declared stronger than an authority. |
+| `policy.resolve(kind, query, rules)` | The decision plus the whole trace: `winner`, `suppressed`, `overrode`, `conflicts`, `explain`. |
+| `policy.unusableRules()` · `unsupportedScopes()` · `unsetKinds()` | The three honesty reports. A rule this build cannot honour is NAMED, never silently dropped; a kind a reader asks for that no rule sets is named too, because a reader falling back forever looks identical to one that is working. |
+| `readPolicy(policy, kind, scope, opts)` | rule → config → constant, through injected `rule` / `config` / `journal` ports. |
+| `policyOrDefault(policy, input, apply)` | A resolved value that cannot be APPLIED is the same kind of gap: recorded, and the default takes over. A default that also fails still throws — that is our bug, not a misconfiguration. |
+| `generatePolicyMarkdown` · `describePolicy` | The policy as committed prose, and as the bounded instructions an agent gets at connect. Every count and the precedence sentence are derived. |
+| `observeJournal` / `reflect` / `curate` / `promote` / `demote` / `playbookRules` | The learning loop. A promoted learning enters at whatever tier the policy calls **advisory**, so it can only ever fill silence. |
+| `journalRowForEvent` | The other three signals' missing input: real lifecycle events as countable rows. |
+| `rulesToSeed(seed, existing)` | Seeding idempotent by id AND by coverage. |
+| `runPolicyAdapterConformance(harness)` | The suite every storage adapter passes, answering with a report rather than an exit code. |
+| `@geonosis/policy/permissions` | `definePolicies` / `hasPermission` / `resolvePermissions` / `checkPermissions` / `createPolicyCatalog` / `expandPolicies`. |
+| `@geonosis/policy/medusa` · `/drizzle` | Two stores behind the same ports. Neither imports the store it adapts. |
+
+## Migrating dielime's rules engine, in five lines
+
+1. `lib/rules.ts` → `definePolicy({ tiers: POLICY_TIERS, kinds: …, scopeKeys: … })`; the twelve
+   `PolicyConstraint` members become twelve `{ kind, schema }`, and `KNOWN_SCOPE_KEYS` +
+   `scopeSpecificity` both disappear into `scopeKeys` (vaguest first — the weight is the position).
+2. `lib/read-policy.ts` → `readPolicy(policy, kind, query, { fallback, …adapter })`; the SLA tier
+   dereference becomes `isReference` + `dereference` on the `approvalSlaHours` kind.
+3. `lib/config-store-binding.ts` → `createMedusaPolicyAdapter({ container, moduleKey, bindings })`
+   with `configRow(namespace, key)`; drop `positive()` from every binding — the kind's schema now
+   refuses junk once, for the rule layer too.
+4. `lib/learning.ts` → the same functions; `playbookRules(policy, playbook)` takes the policy, and
+   `journalRowForEvent(name, data, { subjectKeys, actorKeys })` takes the fifteen event names' keys.
+5. `modules/rules-engine/service.ts` keeps `MedusaService` and its three models, and loses the
+   mapping: `listActiveRules()` is the adapter's `rule.rules()`, and `resolve()` is `policy.resolve`.
+
+`proofs/022-W7-parity/` lists every one of its 65 kernel cases against this package, the ten that
+stay consumer-side, and the seven behaviours that deliberately differ.
+
+## during.day does not adopt this, and here is the measurement
+
+Its thresholds are lint-enforced constants (`ARTICLE XIII §13.3`, `constants-in-constants-file`), so
+the obvious reading is that they are policy waiting for a home. They are not. All 34 `constants.ts`
+files under `packages/` and `apps/` were enumerated: every `SCREAMING_SNAKE` export is a Tailwind
+class, a cache TTL or KV prefix (`SESSION_COOKIE_CACHE_SECONDS`, `PLACEMENT_CACHE_SECONDS`), a regex,
+a literal defaults record (`INVOICE_DEFAULTS = { title: 'INVOICE' }`), or a UI enum.
+`grep -E '_LIMIT|_THRESHOLD|MAX_|_CAP'` across all 34 returns nothing.
+
+None of them carries an authority, a subject or a reason, which is exactly what separates a policy
+rule from a constant. §13.3 is a law about WHERE a constant lives, not about thresholds a tenant may
+set. What that repo could adopt today, without changing a line of behaviour, is the shape of the
+call — its constant passed as `fallback`, so the gap becomes countable — and that is worth precisely
+as much as its journal is fed, which today is not at all.
+
+**D-027 status: one consumer with pull.** C3 of `docs/challenge-2026-08-30.md` ranked this behind
+`@geonosis/integrations` for that reason and it was right to; this package ships inside 1.0.0 with
+dielime's kernel as its only live consumer and musa's lattice as a second fixture, not a second
+consumer. It is DONE when dielime depends on the published version and has deleted its `lib/`.
+
+## What it deliberately does NOT do
+
+- **No global registry.** Upstream's `definePolicies` writes into three `globalThis` objects keyed by
+  name with no duplicate check, and rewrites the caller's objects in place. `createPolicyCatalog`
+  is local and refuses a name already taken.
+- **No store.** Rules, config rows and journal entries all arrive through ports. That is what lets
+  every check in the conformance suite run without a booted server.
+- **No opinion about your tiers.** Including the one that looks universal: whether an unmarked rule
+  may be overridden is `overridableByDefault`, because the two consumers answer it oppositely.

package/dist/chunk-JICJ4XEX.js

@@ -0,0 +1,17 @@
+// src/rows.ts
+var toPolicyRule = (row) => ({
+  constraint: { kind: row.constraint_kind, value: row.constraint_value },
+  id: row.rule_key,
+  // Only `false` is worth carrying: `true` is the default a policy declares, and writing it back
+  // would make a rule that never said anything indistinguishable from one that agreed.
+  ...row.overridable === false ? { overridable: false } : {},
+  reason: row.reason,
+  ...row.scope ? { scope: row.scope } : {},
+  tier: row.tier
+});
+var toPolicyRules = (rows) => rows.filter((row) => (row.status ?? "active") === "active").map(toPolicyRule);
+
+export {
+  toPolicyRule,
+  toPolicyRules
+};

package/dist/drizzle/index.d.ts

@@ -0,0 +1,43 @@
+import { P as PolicyQuery, A as Awaitable, a as PolicyRuleRow, b as PolicyAdapter } from '../types-DzC5zTZ8.js';
+
+/**
+ * A drizzle table, behind the ports the kernel reads.
+ *
+ * Nothing here imports `drizzle-orm`. The query is the store's — a repo whose law says queries are
+ * builders living in its own data layer would not accept one written in a dependency, and a package
+ * that carried the ORM would be unusable in the other consumer's runtime. What this contributes is
+ * the column contract, the mapping, and the posture: a store that is down answers with nothing and
+ * changes no decision.
+ */
+/** The columns the kernel reads. Declared once, so a table and a mapper cannot drift apart. */
+declare const policyRuleColumns: {
+    readonly constraint_kind: "text";
+    readonly constraint_value: "json";
+    readonly overridable: "boolean";
+    readonly reason: "text";
+    readonly rule_key: "text";
+    readonly scope: "json";
+    readonly status: "text";
+    readonly tier: "text";
+};
+/** The journal's columns. There is no `rejected` one: a rejection is written into `error`. */
+declare const policyJournalColumns: {
+    readonly actor_id: "text";
+    readonly actor_kind: "text";
+    readonly error: "text";
+    readonly event_name: "text";
+    readonly fell_back_to: "json";
+    readonly op: "text";
+    readonly subject: "text";
+};
+type DrizzlePolicyAdapterOptions = {
+    config?: (kind: string, query: PolicyQuery) => Awaitable<unknown>;
+    /** Absent when the store has no journal table. Half an adapter is honest; a silent drop is not. */
+    journal?: (row: Record<string, unknown>) => Awaitable<unknown>;
+    rules: (filter: {
+        status: string;
+    }) => Awaitable<readonly PolicyRuleRow[]>;
+};
+declare const createDrizzlePolicyAdapter: (options: DrizzlePolicyAdapterOptions) => PolicyAdapter;
+
+export { type DrizzlePolicyAdapterOptions, createDrizzlePolicyAdapter, policyJournalColumns, policyRuleColumns };

package/dist/drizzle/index.js

@@ -0,0 +1,54 @@
+import {
+  toPolicyRules
+} from "../chunk-JICJ4XEX.js";
+
+// src/drizzle/index.ts
+var policyRuleColumns = {
+  constraint_kind: "text",
+  constraint_value: "json",
+  overridable: "boolean",
+  reason: "text",
+  rule_key: "text",
+  scope: "json",
+  status: "text",
+  tier: "text"
+};
+var policyJournalColumns = {
+  actor_id: "text",
+  actor_kind: "text",
+  error: "text",
+  event_name: "text",
+  fell_back_to: "json",
+  op: "text",
+  subject: "text"
+};
+var attempt = async (what) => {
+  try {
+    return await what();
+  } catch {
+    return void 0;
+  }
+};
+var toRow = (entry) => ({
+  actor_kind: "system",
+  ...entry.rejected ? { error: `rejected ${JSON.stringify(entry.rejected.value)}: ${entry.rejected.reason}` } : {},
+  event_name: entry.event,
+  fell_back_to: { constraintKind: entry.kind, value: entry.fellBackTo },
+  ...entry.op ? { op: entry.op } : {},
+  ...entry.subject ? { subject: entry.subject } : {}
+});
+var createDrizzlePolicyAdapter = (options) => ({
+  ...options.config ? { config: { get: async (kind, query) => attempt(() => options.config?.(kind, query)) } } : {},
+  ...options.journal ? {
+    journal: {
+      write: async (entry) => void await attempt(() => options.journal?.(toRow(entry)))
+    }
+  } : {},
+  name: "drizzle",
+  rule: { rules: async () => toPolicyRules(await options.rules({ status: "active" }) ?? []) }
+});
+export {
+  createDrizzlePolicyAdapter,
+  policyJournalColumns,
+  policyRuleColumns
+};