refactor: unify user chain data port access

This commit is contained in:
jxxghp
2026-08-24 04:16:09 +08:00
parent 48e796cab7
commit a13c96d30b
6 changed files with 54 additions and 15 deletions
+5 -4
View File
@@ -131,10 +131,11 @@ Session. `app/db/adapters/` is the concrete persistence-adapter layer: it may
depend on Application-owned Protocols, UoW/Session and Oper implementations.
This deliberate dependency inversion is the only `DB implementation ->
Application contract` direction; Application must remain free of DB imports.
Workflow-domain consumers use the named `get_chain_*_port()` functions from
`app/application/chain/data.py`; they must not alias migration-time `*PortProxy`
classes back to database Oper names. Those proxy classes remain compatibility
boundaries while the other established Chain domains migrate independently.
Migrated workflow, user, interaction and messaging Chain consumers use the named
`get_chain_*_port()` functions from `app/application/chain/data.py`; they must not
alias migration-time `*PortProxy` classes back to database Oper names. Those
proxy classes remain compatibility boundaries while the other established Chain
domains migrate independently.
### Adapter boundaries