ekwo-os 0.12.0 → 0.12.1

package/README.md

@@ -517,7 +517,7 @@ exactly six fields:
   "organization": "My Organisation",
   "country": "<cc>",
   "edition": "community",
-  "schema_version": "0.12.0",
+  "schema_version": "0.12.1",
   "contact_email": "you@example.com"
 }
 ```

package/dist/assets/expected-objects.json

@@ -1,6 +1,6 @@
 {
-  "schemaVersion": "0.12.0",
-  "migration": "20261010181201",
+  "schemaVersion": "0.12.1",
+  "migration": "20261011082857",
   "socle": {
     "schema": "public",
     "tables": [
@@ -793,6 +793,14 @@
             "name": "id",
             "type": "uuid"
           },
+          {
+            "name": "invoice_accent_color",
+            "type": "text"
+          },
+          {
+            "name": "invoice_logo_position",
+            "type": "text"
+          },
           {
             "name": "language",
             "type": "character(2)"
@@ -3905,6 +3913,10 @@
         "name": "assert_writes_into_known_company",
         "arguments": "p_company_id uuid"
       },
+      {
+        "name": "attachment_is_filing_deposit_file",
+        "arguments": "p_attachment_id uuid"
+      },
       {
         "name": "audit_changes",
         "arguments": ""
@@ -4713,6 +4725,10 @@
         "name": "statement_account_matches",
         "arguments": "p_company_id uuid, p_statement_code text, p_from date, p_to date"
       },
+      {
+        "name": "statement_rule_catches",
+        "arguments": "p_rule statement_line_rules, p_code text, p_account_type account_type, p_balance numeric"
+      },
       {
         "name": "suggest_combination",
         "arguments": "p_transaction_id uuid"
@@ -4832,6 +4848,10 @@
       {
         "name": "version_at_least",
         "arguments": "p_version text, p_floor text"
+      },
+      {
+        "name": "year_result_account",
+        "arguments": "p_company_id uuid, p_balance numeric"
       }
     ],
     "policies": [
@@ -7312,6 +7332,17 @@
           "authenticated": [],
           "service_role": []
         },
+        {
+          "name": "attachment_is_filing_deposit_file",
+          "arguments": "p_attachment_id uuid",
+          "anon": [],
+          "authenticated": [
+            "execute"
+          ],
+          "service_role": [
+            "execute"
+          ]
+        },
         {
           "name": "audit_changes",
           "arguments": "",
@@ -9412,6 +9443,17 @@
             "execute"
           ]
         },
+        {
+          "name": "statement_rule_catches",
+          "arguments": "p_rule statement_line_rules, p_code text, p_account_type account_type, p_balance numeric",
+          "anon": [],
+          "authenticated": [
+            "execute"
+          ],
+          "service_role": [
+            "execute"
+          ]
+        },
         {
           "name": "suggest_combination",
           "arguments": "p_transaction_id uuid",
@@ -9721,6 +9763,17 @@
           "service_role": [
             "execute"
           ]
+        },
+        {
+          "name": "year_result_account",
+          "arguments": "p_company_id uuid, p_balance numeric",
+          "anon": [],
+          "authenticated": [
+            "execute"
+          ],
+          "service_role": [
+            "execute"
+          ]
         }
       ],
       "defaultPrivileges": []

package/dist/assets/migrations/20261010160429_an_invoice_wears_the_colour_of_its_company.sql

@@ -0,0 +1,38 @@
+-- Ekwo OS — an invoice wears the colour of the company that sends it.
+--
+-- `@ekwo-ai/invoice-pdf` prints every invoice in one layout and takes a small
+-- theme: an accent colour and the side of the logo. Until now only the caller
+-- could hand it one, so the PDF of `ekwo doc pdf`, of the MCP tool
+-- `render_invoice_pdf` and of any other client came out in the brick's default
+-- whoever had sent it. Which colour a company prints in is a fact about that
+-- company, the same for every surface that renders its invoices; it belongs
+-- beside its logo, on `companies`.
+--
+-- **Two columns, both nullable.** Null is the brick's default, which is the
+-- answer for every company that exists today and needs no backfill. The
+-- typeface of the theme stays out: it is a file, and the core keeps none.
+--
+-- **The same constraints the brick applies.** A colour is `#rrggbb` and a side
+-- is `left` or `right`; anything else would be stored here and refused at the
+-- first rendering, so it is refused at the write instead.
+--
+-- **Who may write it** is who may write the company: `companies_update`
+-- judges the row, `company.write`. No grant changes — the table is already
+-- granted, and a column added to it is covered by that grant.
+
+alter table companies
+  add column if not exists invoice_accent_color  text,
+  add column if not exists invoice_logo_position text;
+
+alter table companies
+  add constraint companies_invoice_accent_color_hex
+  check (invoice_accent_color ~ '^#[0-9A-Fa-f]{6}$');
+
+alter table companies
+  add constraint companies_invoice_logo_position_side
+  check (invoice_logo_position in ('left', 'right'));
+
+comment on column companies.invoice_accent_color is
+  'The accent colour of this company''s invoice PDF, written #rrggbb: the title, the rules and the bands of the layout. Null is the default of @ekwo-ai/invoice-pdf.';
+comment on column companies.invoice_logo_position is
+  'The side of this company''s invoice PDF its logo is printed on: left or right. Null is the default of @ekwo-ai/invoice-pdf (left).';

package/dist/assets/migrations/20261010203452_a_filing_file_is_read_as_a_filing.sql

@@ -0,0 +1,95 @@
+-- Ekwo OS — the file of a declaration is read as a declaration.
+--
+-- `filings.read` was granted apart from `documents.read` on purpose: what a
+-- company declared is not the same secret as what it books
+-- (`20260917150000`), and the deposits that record each send ask it
+-- (`20260918110000`). The two files of a deposit — what was sent, and the
+-- receipt that came back — are rows of `attachments`, and every row of
+-- `attachments` was read through `documents.read` and written through
+-- `documents.write` (`20260913083216`). So a member whose `filings.read` was
+-- withdrawn and who kept `documents.read` saw no deposit, and still read the
+-- declaration that went and the acknowledgement of the administration.
+-- Decision 0039 left it as an open item; this closes it.
+--
+-- **Which files.** Two kinds, and either is enough:
+--
+--   - an attachment **of a declaration** (`entity_type = 'tax_filing'`), which
+--     is where the two files of a deposit are kept, from the moment they are
+--     uploaded and before the deposit names them;
+--   - an attachment **a deposit names**, as `sent_file_id` or
+--     `acknowledgement_id`, wherever it was pinned: the trigger of
+--     `20261007113412` keeps it in the declaration's company and does not
+--     ask its `entity_type`.
+--
+-- Such a file is read with `filings.read` and written — uploaded, changed,
+-- moved, deleted — with `filings.write`, the capability that writes deposits.
+-- Every other attachment keeps `documents.read` and `documents.write`. The
+-- two policies of a client handing a piece over (`attachments_deposit`,
+-- `attachments_select_own_deposit`, `20260918113807`) are untouched: they
+-- only ever reach a piece on the company itself, or one the caller filed.
+--
+-- **Why a definer function asks about the deposit.** A policy reads other
+-- tables under the caller's own policies, and the deposits ask
+-- `filings.read`: an `exists` written in the policy would find no deposit for
+-- precisely the member this is about, and let the file through as an
+-- ordinary one. `attachment_is_filing_deposit_file()` looks past the
+-- policies of `tax_filing_deposits`, answers about one attachment and nothing
+-- else, and is two probes of the indexes `20260918110000` put on the two
+-- columns. On a shared installation it answers only about a company the
+-- caller may know of (`may_know_of_company()`, decision 0065): an id of
+-- another tenant's file gets the answer an id of nobody gets. The capabilities are compared the way `20260918141627` compares
+-- them — a sub-select run once per statement — and `attachments` is a table
+-- read file by file, never walked by a report.
+
+create or replace function attachment_is_filing_deposit_file(p_attachment_id uuid)
+returns boolean
+language sql
+stable
+security definer
+set search_path = public, pg_temp
+as $$
+  select exists (select 1 from tax_filing_deposits d join tax_filings f on f.id = d.filing_id
+                  where d.sent_file_id = p_attachment_id and may_know_of_company(f.company_id))
+      or exists (select 1 from tax_filing_deposits d join tax_filings f on f.id = d.filing_id
+                  where d.acknowledgement_id = p_attachment_id and may_know_of_company(f.company_id));
+$$;
+
+comment on function attachment_is_filing_deposit_file(uuid) is
+  'Whether a deposit of a declaration names this attachment as the file that was sent or as the receipt. Definer, because the policy of attachments asks it for callers who may not read the deposits — which is the case it exists for; it answers about one id and nothing else, and about a company the caller may not know of as about nobody (decision 0065).';
+
+revoke execute on function attachment_is_filing_deposit_file(uuid) from public, anon;
+grant execute on function attachment_is_filing_deposit_file(uuid) to authenticated, service_role;
+
+drop policy attachments_select on attachments;
+create policy attachments_select on attachments
+  for select using (
+    case
+      when entity_type = 'tax_filing' or attachment_is_filing_deposit_file(id)
+        then company_id = any ((select companies_with_capability('filings.read'))::uuid[])
+      else company_id = any ((select companies_with_capability('documents.read'))::uuid[])
+    end
+  );
+
+comment on policy attachments_select on attachments is
+  'documents.read, except for the files of a declaration — attached to a tax_filing, or named by a deposit as what was sent or the receipt — which are proof of filing and read with filings.read, like the deposits themselves.';
+
+drop policy attachments_write on attachments;
+create policy attachments_write on attachments
+  for all using (
+    case
+      when entity_type = 'tax_filing' or attachment_is_filing_deposit_file(id)
+        then company_id = any ((select companies_with_capability('filings.write'))::uuid[])
+      else company_id = any ((select companies_with_capability('documents.write'))::uuid[])
+    end
+  )
+  -- A check is asked once per row written, as `20260918141627` leaves it.
+  with check (
+    case
+      when entity_type = 'tax_filing' or attachment_is_filing_deposit_file(id)
+        then has_capability(company_id, 'filings.write')
+      else has_capability(company_id, 'documents.write')
+    end
+  );
+
+comment on policy attachments_write on attachments is
+  'documents.write, except for the files of a declaration — attached to a tax_filing, or named by a deposit — which are written with filings.write, the capability that records a deposit. Moving a file onto a declaration needs both: the old row is asked documents.write, the new one filings.write.';