Repository navigation
Releases
v2026.11.16
Highlights
Accounting Core (Phases 1 & 2)
- General ledger & periods: chart of accounts (
ledger_accountshierarchy), balancedjournal_entries, one-time reversals, trial balance & running account ledgers, and closed-month locking. - Credit & debit notes: typed corrective notes linked to the original submitted invoice, with
invoice_offsetsand over-credit / cross-party guards.
Project Execution & Costing (Phases 1 & 2)
- Task trees & milestones: hierarchical
project_tasks(cycle-guarded), timesheet hour rollups, andproject_milestones. - Issues, frozen reports & execution:
project_issues(PI-log), immutable publishedproject_reportswith point-in-time figures, and/projects/{id}/executionper-currency cost/billing rollups.
Better First-Run & Agent Experience
- Video walkthrough: Oryh Demo — Change the Rules. Run the Order. Verify the Shipment.
- Optional sample workspace (
scripts/seed_sample.py): load fictional Northwind Instruments master data, published discount/approval rules, quotes, orders, open invoice, project, and posted ledger entry in one command:docker compose exec api python scripts/seed_sample.py - CI & multi-arch GHCR images: automated
pytest+frontendCI workflow plus multi-arch (linux/amd64,linux/arm64) release images published toghcr.io/aie-enginehub/oryh-apiandghcr.io/aie-enginehub/oryh-console.
Links
- Hosted service: https://oryh.ai (China: https://oryh.cn)
- Discord: https://discord.gg/dH38JwJUe
- X: https://x.com/OryhAI
- YouTube: https://www.youtube.com/@Oryhai
v2026.11.3
ORYH's public open-core release for self-hosted deployments. Agents read the workspace's natural-language rules and decide how work proceeds; the server records business facts and enforces structural and accounting integrity.
Highlights
- Budgets and cost centres. Record budget plans and changes, inspect execution and cash plans, and scope spending by cost centre. Execution reports progress for an agent to interpret against the workspace's rules. The agent decides when to raise an alert and whom to notify.
- Order-linked points redemption. A points-funded discount records the redemption that paid for it. Reversals retain their ledger references, and invoices preserve the order/customer relationship. Eligibility and the number of points returned follow the workspace's policy.
- Workspace state vocabulary. Business checks read states by their declared roles, supporting renamed lifecycle states. Lead conversion, quotation outcomes, billing-account closure and related decisions follow agent instructions rather than fixed server-side policy.
- Desktop OAuth and MCP compatibility. Opt-in public-client registration supports WorkBuddy callbacks and IP-loopback desktop callbacks. Login, explicit consent, PKCE S256 and one-use authorization codes remain required. MCP initialization negotiates a supported protocol revision.
- Updated agent skills and API references. Budget, billing, CRM, quotation and master-data instructions reflect the separation between stored facts and agent-controlled decisions.
Upgrade notes
Back up the database before upgrading. The migration head is 20261101_0107, joining the budget-policy and desktop OAuth branches without rewriting either migration history.
Changes since v2026.10.25 add budgets, budget changes, cost centres, points-redemption references and public OAuth client metadata. Migration 20261029_0106 removes the retired budget_alerts table and budgets.alert_percents; preserve any alert history you need before migrating. Existing todos remain.
API integrations should account for these changes:
- The budget-alert list and sweep endpoints are retired. Agents read execution progress and the workspace's rule, then record the appropriate todo.
- Writers explicitly supply
cost_center_idwhen a document should book against a centre; the server no longer infers one from linked records. - Agents choose policy-dependent conversion, quotation, points and closure decisions using the updated skills and API contracts.
Dynamic OAuth client registration defaults to disabled. Enable it deliberately with ORYH_OAUTH_DYNAMIC_REGISTRATION_ENABLED=true in the running API environment and restart the API. Discovery then advertises /oauth/register. Registration records public client metadata; users still authenticate and consent before access is granted.
Validation
The exact published export passed the private-infrastructure scan, English-prose check and build-input validation, followed by 1,886 passing tests and 33 skips. Skipped checks are not claimed as verified. These results cover the exported standalone source; actual desktop-client acceptance and a live production deployment are outside this release's validation scope.
Source
Public source commit: dc8723c52fdf5ab0b6491a8f88e50c42d161c29e.
This release contains the allowlisted self-hosted open core. Private SaaS administration, cloud operations, hosted deployment records and the marketing website remain excluded.
v2026.10.25
ORYH's public open-core release for self-hosted deployments. The server keeps business records and audit facts; agents read the workspace's natural-language rules and decide how work proceeds.
Highlights
- Contract sides are explicit. A purchase contract can be filed before its vendor exists in master data. Snapshot-only contracts state
purchaseorsales; scoped permissions follow that side, including related documents and searches. - Contract execution reports business facts. Draft, cancelled and voided documents do not inflate execution totals. Amounts remain separated by currency, and repeated product lines are aggregated correctly.
- Signed agreements retain their evidence. Quoted wording cannot be rewritten in place after signing, and signed originals remain linked. Interpretations, references and page annotations remain editable. Supplement and renewal links must point to live contracts on the same side and cannot form cycles.
- Deal and customer records retain provenance. Deal parties and project links are supported, with one project per opportunity and uniqueness for undated customer relationships.
- English development resources, multilingual behavior preserved. Development prose and skill instructions have been converted to English, with regenerated API references. Chinese runtime text and multilingual fixtures remain in explicit locale resources; applied migration bytes remain unchanged.
This release also includes changes delivered in the public source updates since the previous GitHub Release: delegated credentials cannot grant more than their issuer holds; idempotent request replays recheck authorization; business rules can be read for the date they govern; and channel-order imports land as drafts.
Upgrade notes
- Back up the database before upgrading. The standard Compose startup runs Alembic migrations; this release's head is
20261024_0101. - Migration
20261019_0100refuses existing duplicate projects for one opportunity or duplicate undated customer relationships. Resolve the reported records, then rerun the migration; it does not merge business records automatically. - Migration
20261024_0101stores each contract's side and preserves its previous classification. Existing contracts with only a counterparty-name snapshot retainsales; the migration reports counts for review. An authorized user holding both contract sides can correct a snapshot-only contract or link its vendor, subject to existing execution links. - API clients creating snapshot-only contracts must provide
side. Clients must also respect the signed-wording and signed-original constraints described above.
Validation
The exact published export passed the privacy, English-prose and build-input checks, followed by 1,752 passing tests and 29 skips. Skipped checks are not claimed as verified. This release does not claim a new production deployment or live database migration test.
Source
Public source commit: e7d22e8b0558eaddef2f0389cc5fdd1895a9b444.
The release contains the allowlisted self-hosted open core. Private SaaS administration, cloud operations, hosted deployment records and the marketing website are not included.
v2026.10.7.5
One table of business rules, and the hosted agent's grants are a role
Two migrations reach the public tree (20261006_0097, 20261007_0098). What changes is where a workspace's own rules live, who reads which of them, and what the hosted flow agent may do on the workspace's behalf.
Business rules: one table, four kinds
/policies and /workflow-definitions are gone. Both become rows of one table, business_rules, each row of one kind answering one question:
kind |
answers | read by |
|---|---|---|
approval_flow |
who looks at a submitted document next, and when it is final | the flow agent |
data_rule |
what a document must carry to be filed at all | the submitter's agent while filling; the flow agent once before the first assignment |
linkage |
what happens elsewhere when a document reaches a state | the flow agent, and the desk that completes it |
policy |
the company's standing rules, keyed by their own code |
everyone, by code or category |
A scoped kind is keyed by (entity_kind, object_type, name) and gets a generated code such as approval_flow:builtin:timesheet_header:default; a policy keeps its own code and category. All four share one lifecycle — draft, published, superseded, repealed — one in_force_on read across versions, one /publish that closes the previous version in the same transaction, and /repeal and /visibility that never edit a word. Publishing a scoped kind needs workflows.publish; a policy needs policy.publish.
Migration 0097 moves every policy and workflow definition into the table whole, keeping version numbers, effective periods and the rule_code/rule_version a todo or document pinned; 0098 drops workflow_definitions. Behaviour change: /policies* and /workflow-definitions* answer 404 — read GET /business-rules?kind=policy and ?kind=approval_flow. A business object's detail carries rules where it carried workflow_definitions.
A workspace that published before the kinds existed has one approval_flow whose text also carries its submission requirements. The submit skills read only that section until the administrator publishes it as a data_rule; the setup report's rules.<type>.data_rule_missing_but_flow_has_requirements says which types still owe one.
A shipped catalog of drafts
rules/<kind>/<object_type>.md is a catalog of sixteen starting points — an approval flow, a data rule and, where it applies, a linkage for each shipped document type, in English and Chinese. Every workspace is seeded with them as drafts (origin=catalog); nothing is published for a workspace and nothing a workspace edited or published is ever touched again. A draft nobody touched follows the catalog; a withdrawn file withdraws its untouched draft.
The hosted flow agent holds a role
The hosted flow agent's grants were a platform constant. They are now the shipped default of a system role, hosted_flow_agent, provisioned for every workspace beside admin and member and edited by the administrator like any other: the platform-issued key reads the role on each request, the key row shows what the role says, the driver picker offers what the role covers. No person can be invited into it and it cannot be deleted. The default now carries shipment.manage and inventory.manage, so a linkage that says "a shipment draft is raised at confirmation" is executed by the agent itself — a draft 1:1 from the order's lines, the hold on its stock, a todo for the warehouse — and falls back to the todo with a note naming the grant when the workspace narrowed the role. Not invoice.manage: the agent moves documents without editing a word of them.
Skills
oryh-business-rules(gatepolicy.manage): write, publish, amend, re-scope or repeal any kind, and split a pre-kinds workflow definition into its kinds.- Every flow skill reads the three scoped kinds by kind and scope and cites the rule it followed (
rule_code,rule_version); the order flow raises the shipment when the linkage says so. - The shared fragment
skills/_common/business-rules.mdis the one place that says which agent reads which kind. oryh-skill-authorclassifies a sentence by kind before it becomes a skill.
Console
The object-types page lists rules by kind. The publish drawer opens on the version in force, or on the catalog's draft when nothing is in force, shows the lines a draft drops and warns when it replaces everything; it publishes policies (code, category, title, date of force) under policy.publish. Each row carries the acts its status allows: release a draft, repeal the version in force, change who may read any published version.
Under the hood
- The setup report gains
rules.<type>.{approval_flow,data_rule,linkage}.{published,version}; an object-typePATCHthat changes the state machine writes arule.machine_changedaudit row. STATE_ROLESknowssubmitted,confirmed,cancelledon sales orders andquotingon opportunities.- The Docker image carries
rules/besideskills/, and a test pins it.
v2026.9.25.1
Shared paper is read by grant, and a side effect fixes its source
One migration reaches the public tree (20260924_0096, seven indexes,
idempotent). What changes is who may read the workspace's shared
documents, what a settlement or a stock posting freezes, and a first round
of fixes asked for by a client team driving the API through an agent.
Read grants for shared documents
Personal documents (timesheets, claims, leave, requests, quotations,
orders, the pipeline) have been read by their person, by whoever they were
routed to, or by a read_all grant since v2026.9.24. Shared documents were
still read by membership alone: an outside account holding only
business_object.write:warranty_card read every other vendor's invoice,
the employees' internal order follow-ups and every shipment.
Each shared family now has a read capability: invoice.read[:direction],
payment.read, purchase_order.read, shipment.read, inventory.read
(positions, ledger, picklists), business_object.read:<type>,
billing_account.read. member holds them all by default and the catalog
sync delivers them to existing workspaces. The desk that writes a family
reads it, and a scoped grant reads its scope only: invoice.manage:sales
reads sales invoices, business_object.write:warranty_card reads warranty
cards; payroll.read reads payslips on top of the existing gate. A
credential holding none of them reads what names it, what it wrote and what
was routed to it. Business-object links need both ends readable; the object
directory's counts follow the same rule. Behaviour change: a
workspace-made role that only writes a family no longer reads the families
it does not write — add the read grant; the setup report's role-sync block
names the reads no ordinary role holds.
A settlement or a stock posting fixes what it measured
A deep test on real PostgreSQL found seven ways a permitted call could make
the ledger and its source disagree. All were the same shape: the side
effect had happened and the record it measured was still editable.
- A settled invoice or payment keeps its amounts, currency, billing
account and party while anything is applied against it (409). Reverse
the applications first, or record the difference as its own document. - A draft is never settled: the payment and every invoice, claim or payment
it targets must have left their machine's editable states. Billing
accounts are exempt. - A shipment that has posted stock is the ledger's source: its lines cannot
be added, changed or removed, and its direction, orders, facility and
picklist are frozen. Tracking numbers, dates, remarks and status still
move. - Settlement lines are money to the cent: more than two decimals is a 422,
so what the API sums is what the database stores. - A fin-account register links payments in the account's own currency,
single and batch; an account with lines or a balance keeps its currency. - Fulfilment draws each (product, sku) pool down once; a leg written
against the product alone serves generic and SKU lines from one pool. - A stock hold's order line must be a live line of that order selling the
position's goods; otherwise 422 and available-to-promise is unchanged.
Each has a regression in tests/test_deep_test_findings_2026_09_24.py.
Lowering a credit limit below current exposure stays allowed on purpose.
What an agent-driven client asked for
- Object-directory counts follow the reader's visibility.
GET /auth/mecarriespermissions_fingerprint, a digest of the
effective grant set, so a client knows when to drop what it cached.- MCP
tools/listcarries annotations: six read toolsreadOnlyHint,
oryh_requestdestructive,upload_attachmentidempotent. /submit,/restore,/revise,/send,/publish,/repeal,
/convert,/quote,/releasetake no body; optional bodies are
declaredBody(default=None)so the contract keeps their fields.employee_nameon todos, timesheets, leave, claims and requests;
order_noon order lines; product id, name and SKU code on inventory
movements — read live, never stored.GET /capabilitiesnames the collections each capability governs.GET /my/skills/manifestmeta.withheldnames targeted skills the
caller holds the capability for but was not named to.- The gateway answers API and MCP upstream failures with a JSON 503 and
Retry-After; the standalone gateway forwards/oauth,/mcpand the
well-known paths like the hosted one. - An expired OAuth consent renders a page with "open again" and "back to
the client".
Under the hood
app/api/commonis a layered package; 51 Update request models are
generated from their base models withpartial_model; line, verb and
plain-read routes are declared as data and built by one factory. The
OpenAPI document is byte-identical across all of it.- Todo-target totals, the fulfilment backlog and the product-matching
catalog matcher read in batches or from a per-tenant cache instead of
per row. - The dev-dependency advisories on
js-yamlandvitestare closed
(4.3.2, 4.1.11); the deprecated 422 status constant is gone.
v2026.9.24
A person's documents are theirs
No migration reaches the public tree this time; what changes is who may
read what, how a document is edited, and what the server computes.
Read visibility: mine, routed to me, or the read-all grant
Every read but payroll was tenant-scoped: belonging to the workspace meant
reading everyone's timesheets, expense claims, leave, purchase requests,
quotations, orders, leads and deals. Now a personal document is read by the
employee it belongs to, by whoever it was routed to (a todo or an approval
fact on it), and by a credential holding the family's read_all — seven new
capabilities: timesheet, leave, expense, purchase, quotation,
order, crm — or a grant that cannot be exercised blind: the family's
advance and the desks downstream of it (shipping, invoicing under any
scope, paying, buying), and tenant.act_for_any_employee. Lines,
adjustments, approval facts, todos (todos.assign reads all), the record of
contact, attachments and the named record's audit trail follow the document.
What you may not read does not exist for you: omitted from lists, 404 on a
direct read or write.
Enforced at the two choke points every handler uses (list_rows,
get_scoped_or_404), so an endpoint written the ordinary way is scoped.
tests/test_read_visibility.py files one document per family as one member
and asks every GET route in OpenAPI as another. Behaviour change: a role
holding only the member defaults sees its own documents; the sales pipeline
is no longer everyone's to read — grant crm.read_all to member for an
open pipeline.
Whole-document saves for every document with lines
POST /expense-claims/{id}/save (header fields and items in one
transaction), and the same for invoices, contracts, bills of materials,
picklists, shipments and opportunities — every document whose create takes
inline lines can now be restated in one call. One engine: a row naming an
id is that line, changed only in the fields it states; a row without an
id is validated through the line's create schema and built by the POST's
constructor; a live row not listed is removed. What a line IS (its product
on a shipment) cannot change in place. expected_revision from the detail,
409 when stale, ?validate_only=true writes nothing. The four existing
/save routes now diff kept rows on stated fields too.
Line amounts are the server's arithmetic
A priced line's amount is quantity × unit_price, computed and stored;
a gift is 0; a stated amount that disagrees is a 422 with the arithmetic
(a line-level discount is an adjustment); only an unpriced line keeps a
lump sum. Applied to quotations, orders, purchase requests and orders,
invoice lines and deal lines, on create, PATCH, /save and bulk import
(where a bad line is that row's error). Tax is not derived: tax_rate is a
percentage and amounts may be tax-inclusive, which is the tenant's practice.
Approval flow: the trail is the fact
- A todo for an approval step the trail already decides (approved,
rejected, returned at that round/sequence) is refused with a 409 naming
the decision — the flow agent's next move is to advance the document, not
to re-issue the step. Rework todos are exempt. - A
todos.assignholder may cancel a todo it minted — cancel only, never
complete.
Also
POST /external-product-maps/resolve: a whole import's listings
translated in one call (up to 500), each as of its own date, with the
/product-matchesshortlist for the unmapped ones; the catalog matcher
is loaded once and indexed by word and CJK bigram.- Idempotency: the stored answer is committed before its first byte leaves,
so an instant retry replays instead of meeting a 409. - Plain lists and by-id reads of master data are declared as data
(app/api/registry.py) and built by one factory; the OpenAPI document is
byte-identical.
v2026.9.15
A retry answers what the first attempt did
Two migrations reach the public tree, 0094 and 0095, with a change every
client feels: every write is retry-safe, an MCP client's "disconnect" is a
revocation on the server, and every list can be cut by its dates and its
references.
Every write takes an Idempotency-Key
An agent whose POST timed out after the server committed had one move: read
back and guess. Now every write under /api/v1 (POST, PATCH, PUT, DELETE)
accepts an Idempotency-Key header — a token the client chooses for that one
act, a UUID will do:
- the same key with the same request replays the first attempt's response
(status, body,Idempotency-Replayed: true) for 24 hours and writes nothing twice; - the same key with a different request is a 422 (
idempotency_key_reused) —
a client bug, not silently answered with the first request's result; - a key still in flight is a 409; a 5xx is not remembered, so the retry really runs;
- keys are scoped to the presented credential, so tenants and people never meet on key text.
One pure-ASGI middleware claims the key before the handler runs and stores the
answer after (idempotency_records, migration 0095). OpenAPI documents the
header on every write operation; the MCP oryh_request tool takes
idempotency_key and forwards it. The body-level idempotency_key of
money-moving endpoints stays — it binds to rows, this binds to the HTTP act.
OAuth: disconnect is revocation
POST /oauth/revoke (RFC 7009), advertised as revocation_endpoint. Until
now a client's disconnect only forgot its copy of the token; now the pair is
deactivated the way the person would have done from Access credentials.
Either half — access token, current or just-rotated refresh token — revokes
the whole pair; company service keys are not OAuth tokens and are out of
reach; unknown tokens answer 200 like live ones. The consent fingerprint
column is text (migration 0094): a real client's authorization request
overflowed varchar(128) and the authorize page answered 500 on PostgreSQL.
Lists: every date is a range, every reference a filter
Every paged list carries created_at_from / created_at_thru, and each
document adds its own dates — order_date, promised_date, shipped_at,
invoice_date, due_date, effective_at, expires_at, signed_at … —
as inclusive <column>_from / <column>_thru pairs typed from the column.
References a person actually narrows by (contract, project, currency,
employee, product, SKU, facility, approver, channel) are exact-match filters
named after the column; a non-UUID value on an id filter is a 422. The stock
ledger can finally be read for a period: /inventory-item-details?effective_at_from=….
Unknown query parameters on reads are refused (422 naming what the operation
accepts) instead of silently ignored — GET /products?product_code=X no longer
answers with the unfiltered list.
Whole-document writes
?validate_only=true on every inline create runs every check and writes
nothing. POST /{sales-quotations,sales-orders,purchase-orders,purchase-requests}/{id}/save
restates a document's lines and adjustments as a diff under the detail's
revision (409 when stale). Quotation, order and purchase-order creates take
adjustments[] with the lines; contracts take documents[] and terms[].
Timesheets save atomically with the same revision rule. Picklist, shipment,
contract and BOM lines go through one constructor whether inline or standalone.
Also
- A custom object created past its machine's initial state, or advanced from
there, takes thebusiness_object.advancegrant. - Effect documents remember their definition version; a posted document is
frozen; transfers must net to zero; ledger arithmetic runs under row locks. - NaN and Infinity are refused at the boundary; validation errors are always JSON.
- Skills: refunds link to returns by
reference_no; MCP delivers skill text
only and never reads keys, scripts or re-sync; the query guard walks the
dependant itself (FastAPI 0.141).
v2026.9.11.1
Every ledger row is a business act
Seven migrations reach the public tree, 0087 through 0093, together with
the first phase of sales management, a console data browser, and a change of
principle in how stock and account balances move: no ledger row is typed by
hand any more. Two rounds of end-to-end tests with role agents — a
lead-to-delivery sales loop and a multi-platform e-commerce import — drove
most of the fixes; both reports are in the private tree, the fixes are here.
Stock and account ledgers have doors, not a write endpoint
An operator's agent heard "ship it", skipped the order and the shipment, and
wrote a bare stock movement. The generic write that allowed it is gone:
POST /inventory-item-details and POST /billing-accounts/{id}/entries no
longer exist (both collections stay readable and append-only). Every movement
now comes through the act that causes it:
- goods leave or arrive through a shipment (
POST /shipments/{id}/post-stock, once);
purchase-order goods through/receive; counts throughPOST /inventory-items/bulk; - a hold for an order through
POST /sales-orders/{id}/reserveand/release—
the server writes the reservation pair itself, refuses a position that holds
goods the order does not sell, a hold that would push available below zero,
and a release larger than what is held; - everything else — damage, transfers, loans, production receipts, points
grants and redemptions, balance adjustments — is a tenant-defined
document: an object type whose state machine declaresstock_effector
account_effect{reason, state}, whose payload carries signed lines, and
which posts once throughPOST /business-objects/{id}/post-stockor
/post-entriesfrom the declared state. A correction is a counter-document. - money on an account moves only through
POST /payments/{id}/apply; a points
batch lapses throughPOST /billing-accounts/{id}/expire, which holds the
sweep to its facts (the batch, its expiry, not yet expired, at most the batch).
A new capability, shipment.manage, gates the freight legs so an order
desk can ship what it sold without reaching a position or a count;
inventory.manage implies it, so no existing role changes. Two smaller doors
closed with it: an order that ships by shipments takes its carrier, tracking
number and shipped/signed moments from the shipment (409 on the header
fields), and the submitted approval fact is the server's — a person's
credential records decisions only.
New skills oryh-shipping ("ship it" IS a shipment) and oryh-campaign;
oryh-inventory and oryh-billing-account are rewritten around "every
movement has a door".
Sales management, phase one (0088–0091)
- Campaigns and members; leads and opportunities carry
campaign_id, the
campaign's detail counts leads, conversions and won deals live. - Opportunities gain probability, lost reason, competitor and source; product
lines (/opportunity-items), customer-side roles (/opportunity-contacts),
andPOST /opportunities/{id}/quotebuilds a quotation draft from the lines
with aprice_basisper line. - Activities, events and communication events — the record of contact;
POST /events/{id}/logwrites the activity and holds the event in one
transaction. - Geos and territories: a shipped province template (
POST /geos/seed-template,
GB/T 2260 codes), territories with coverage and members,
GET /territory-resolution?geo_id=; customers and leads carrygeo_idand
land in a territory on their own. skills.calibrate, scopable per skill: the order desk writes one skill's
calibration without holdingskills.manage.
From the simulations
GET /product-matchesscores the phrases a product (and its SKUs) shares
with a platform title, each weighed by its rarity in the catalog, so the
ribbon outranks the printers that share its marketing compound; it names the
SKU a spec token points at (sku_candidates) and reportshas_skustruthfully.- The product map's spec text folds like the title does; an id-carrying lookup
also answers with the title-keyed rows a desk wrote earlier; the order desk
writes, corrects and withdraws undated rows while dated swaps stay with the
catalog desk. - A platform order number becomes one order: linking it to a second order is a
409 unless the caller declaressplit: true; a seller links only its own orders. GET /fulfilment-backlogand the order detail'sfulfilment[]carry
ordered / shipped / outstanding per line — the shortage as a fact the flow
can chase without a promised date. The store list names its warehouses;
a position registers itsfacility_idafter the fact; a USD order carries
no CNY list price.- A line's stored amount is dropped when its price, quantity or gift flag
changes; a person may give themselves a todo; contracts include the whole
family of every collection a skill names; a confirmed order accepts only
fulfilment facts; converting a lead into an existing customer keeps the
contact and re-homes the record of contact.
Orders, console, skills (0087)
POST /sales-orders/{id}/revisecancels a confirmed order the warehouse
cannot ship and opens a new draft that remembers it (supersedes_order_id).- Every paged list accepts
order_by; seven line and adjustment lists gain
paging and sorting. - The console gains a data browser (
/console/data): every collection,
server-side filters from the OpenAPI, any column sortable, create / edit /
delete and document verbs, every write previewed and confirmed first. - 26 person-facing writing skills confirm before they write
(skills/_common/confirm-before-you-write.md); the platform-listing
resolution lives in oryh-product-matching, with each workspace's own
rules in that skill's calibration.
Operations
0092 adds a per-company switch on hosted flow driving and 0093 a
platform_settings table; both belong to the SaaS layer and are inert in a
standalone deployment. A circular import between the audit trail and the
models, invisible to the API process, left alembic unable to import the
tree first; it is resolved lazily now and pinned by an import-order test.
Apache-2.0. This tree is produced from a private repository by an allowlist
export, guarded by a scan for our infrastructure names, an English-only-prose
check, and the exported suite's own pytest run — 1513 passed, 26 skipped
for this release.
v2026.9.7
Descriptions that route, and a todo that says who finished it
Two migrations reach the public tree, 0085 and 0086, together with a
rewritten console and a catalog that is half the size and picks the right
skill slightly more often.
The catalog decides who a skill is for
An agent picks a skill by reading descriptions, so a description is routing
data, not documentation. Forty of them were rewritten to say only what
distinguishes one skill from its neighbours — what the request looks like, and
which sibling to prefer when it does not.
scripts/skill_selection_bench.py is the check on that claim rather than an
opinion about it. It builds before/after catalog prompts from a 42-request task
set and scores a model's picks; twelve runs, two models, three samples each.
The catalog halved — 39 skills / 19,532 chars to 31 / 8,695 — and selection
accuracy did not move (96.7% → 96.7% for the smaller model, 98.4% → 99.2%
for the larger). The one systematic miss it found was real and fixable: "change
how this document routes" went to the policy skill instead of the skill-author
skill, which was a description problem, not a model problem. After sharpening
that pair the smaller model scores 42/42 three times.
0085 — a skill's audience is the catalog's to state
The eight *-approval-flow skills are the unattended flow agent's. They gate
on *.advance, and an administrator holds every capability, so every
administrator's bundle contained eight skills only the runner ever executes.
They now ship targeted with nobody named: the service principal ignores
audience and still receives them, a person receives them only by being named.
Tracking follows the same rule the capability gate already used — a workspace
that set a mode owns it, an untouched default follows the catalog.
If you were driving flows by hand from an administrator's bundle, name yourself
in the skill's audience (POST /skills/{id}/assignments); nothing about your
permissions changed, and approving a single document by hand was never part of
this family.
0086 — a completed todo now says who completed it
Resubmitting a reworked document completes the rework todo it answers. That
path wrote completed_at and not completed_by, so every resubmission left a
row claiming to be finished by nobody, and the integrity audit counted one more
every time.
The code is fixed and the rows already written are repaired from the audit
trail rather than guessed: the same call that forgot the column wrote a
todo.completed audit row with the actor immediately afterwards, and that
actor is the value the column should have held. downgrade is deliberately
empty — putting the nulls back would destroy recovered facts.
A missing record is an answer, not a search
New shared skill guidance (skills/_common/fail-fast-on-master-data.md): when
somebody names a project, product, customer, vendor or facility that is not in
the master data, say so in one sentence and stop. Do not try other
spellings, page the whole list, or quietly substitute the nearest match. The
record's absence is the person's or their administrator's to fix, and only they
know whether the name was wrong or the record is missing.
Console
The tenant console is rebuilt around daily data and CRUD work rather than a
dashboard first: shared list filtering, create-intent handling and record
notices are now components instead of per-page code.
Demo data
A third demo workspace, Northwind Instruments Ltd — thirteen people, nine
roles, entirely in English, for readers who found the two Chinese workspaces
hard to follow. scripts/seed_demo.py --only <slug> seeds one workspace and
leaves the others untouched; --reset still deletes every demo workspace by
email domain, which is a much larger act than it sounds.
Apache-2.0. This tree is produced from a private repository by an allowlist
export, guarded by a scan for our infrastructure names and by the exported
suite's own pytest run — 1413 passed, 26 skipped for this release.
v2026.9.5
A second door, and a stricter house
Five migrations of the private build reach the public tree together, 0081
through 0084. The headline is that an agent can now reach oryh without a
key you pasted somewhere.
OAuth 2.1 and MCP — the second door
POST /mcpis one stateless JSON-RPC endpoint behind the same service
layer everything else uses. No parallel implementation of your business
rules lives there.- MCP clients discover the rest:
/.well-known/oauth-authorization-server
(RFC 8414) and/.well-known/oauth-protected-resource(RFC 9728). They run
authorization code + PKCE, S256 only, in the person's browser and
receive the same interactive key pair the device flow already minted. - The authorization code is the consent's receipt: hashed, ten minutes, spent
once. The consent itself is a nonce bound to the session that saw the page,
stored as aconsent-stage row beside the codes — a consent never
redeems as a code. - A client is a URL and may only be sent back to its own host over https, or
to a loopback address on any port. Nothing is registered in advance.
Archived is history
A bank account entered by mistake, with a mistaken statement imported into it,
was archived — and the agent kept reading its register lines as this month's
cash, because "archived" was only a column value inside the same list.
Now sixteen master-data collections plus financial accounts answer with
active rows unless asked (status=archived for the history, status=all
for both), and a parent's history leaves with it: an archived account's
register lines and an archived position's movements list only when that parent
is named or include_archived_accounts / include_archived_items is passed.
Every such row carries account_status / item_status, and the
reconciliation queue never shows them. Reviving the parent brings the history
back; nothing was lost.
Money
/sales-channels— the key orders arrive under becomes master data
instead of asourcestring scattered across stores, maps and document
links.channel_codeis unique per tenant; the name is unique among active
rows, so archiving frees it.- One bank debit settles a batch. Payroll leaves the bank as one debit for
ten payments and a supplier run does the same, but a register line could
link to one payment only, so the batch sat in the reconciliation queue
forever. A line may now link to the batch — thereference_nothose
payments share — and the server accepts it only when every member moves
money the same way and they sum to the line exactly. The refusal names
the count, the sum and the difference. - A bank charge is a register fact, not a payment. Either as gross/fee/net
on the same line, or as its ownfeeline. Neither needs a payment, and
neither needs the bank entered as a vendor.
The ledger's last defence
POST /shipments/{id}/post-stock was already a once-only bridge. It now takes
a row lock, and behind that a partial unique index refuses a second effect of
the same kind from the same shipment line — so two concurrent callers cannot
both win.
Also
- A generic object may not be named after a shipped collection:
object_type: "product"is refused, pointing at/products. It used to create a shadow
table no order line, price or inventory row could ever point at. - A parked flow subscription can be cleared by the tenant, and clears itself
when the next workflow definition is published. - The catalog gained recipes (bills of materials), pictures backed by the
attachment store, contracts with locatable clauses, and an external product
map that answers by listing title when the platform export carries no ids.