application tier

application-encounters

Forge module wrapping domain-encounters.

Forge module wrapping domain-encounters.

Tierapplication
Roleunclassified (baselined)
Pathcrates/application/encounters
Edition2024
Targetsapplication_encounters, pg_forge_encounters
Public items6 across 0 modules
Tests2

What it is for

application-encounters — wraps domain-encounters.

B-009: before this, migrations() returned Vec::new() and migrate_pending returned Ok(0) while ignoring the pool, so encounter_participants and encounter_state_history (plus the duration/lookup/transition helper functions, crates/domain/encounters/migrations/001_encounters_tables.sql and 002_encounter_participants_party_fk.sql) were never created by anything that actually called this module's own migration path. Mirrors application-research's and application-calendar's pattern exactly.

Note: application-engine's central platform set (crates/application/engine/migrations/073_encounters_vendor.sql) already vendors the base encounters table (identical column/constraint definitions) for ticketing's FK needs — this module's own CREATE TABLE IF NOT EXISTS encounters is therefore a no-op there and only adds the two tables the central vendor deliberately left out (encounter_participants, encounter_state_history) plus the triggers and helper functions. Migration 002 adds a FK from encounter_participants.party_id to parties(id), so it requires the parties table to exist first (see the live-pg test's bootstrap).

No permission_codes() added: domain-encounters (crates/domain/encounters/src/lib.rs) defines no permission/capability constants to draw from — nothing to wire without inventing names.

Capabilities

EncountersModule

application-encounters — wraps domain-encounters.

Item
pub struct EncountersModule
EncountersModule :: fn new() -> Self
EncountersModule :: fn name(& self) -> & 'static str
EncountersModule :: fn version(& self) -> & 'static str
EncountersModule :: fn migrations(& self) -> Vec <MigrationSet>
EncountersModule :: async fn migrate_pending(& self, pool : & PgPool) -> std::result::Result <u32, MigrationError>

How to use it

No examples/ target and no doctest in this crate's rustdoc. The tests listed under Verification are the closest executable usage.

Module structure

No public modules: the crate root is its whole surface.

Public surface

`crate root`

ItemWhat it is
pub struct EncountersModule
EncountersModule :: fn new() -> Self
EncountersModule :: fn name(& self) -> & 'static str
EncountersModule :: fn version(& self) -> & 'static str
EncountersModule :: fn migrations(& self) -> Vec <MigrationSet>
EncountersModule :: async fn migrate_pending(& self, pool : & PgPool) -> std::result::Result <u32, MigrationError>

No pub use re-exports: every item above is declared in this crate.

Boundary

Reaches into domain.

Shares tier application with 120 other crates: application-agreements, application-ai, application-analytics, application-approvals, application-assessments, application-audit-log, application-auth, application-billing, … (120 total).

_What this crate deliberately does NOT own is a judgment. No committed registry records one for it, so none is stated here._

Where it sits

Tier (ontology)application
Architectural role (taxonomy)unclassified (baselined)
Locationcrates/application/encounters
Vocabulary in force (lexicon)current

Tier flow. Which tiers this crate's own edges cross.

flowchart LR
  n_application["application"] --> n_domain["domain"]

Dependencies

Runtime, in this workspace.

CrateTierOptionalOnly on
`application-core`applicationnoalways
`domain-encounters`domainnoalways

Runtime, from outside the workspace.

CrateRequirementFeaturesOptionalOnly on
async-trait^0.1noalways
sqlx^0.8runtime-tokio, postgres, chrono, uuid, jsonnoalways

Development, in this workspace.

CrateTierOptionalOnly on
`application-engine`applicationnoalways
`application-parties`applicationnoalways

Development, from outside the workspace.

CrateRequirementFeaturesOptionalOnly on
tokio^1fullnoalways

Build. None.

Depended on by. Nothing in this workspace.

Signal flow — what reaches this crate, and what it reaches.

flowchart LR
  SELF["application-encounters"]
  SELF -->|development| n_application_engine["application-engine"]
  SELF -->|development| n_application_parties["application-parties"]
  SELF -->|runtime| n_application_core["application-core"]
  SELF -->|runtime| n_domain_encounters["domain-encounters"]
  classDef self fill:#1f883d,stroke:#1f883d,color:#fff;
  class SELF self;

Feature flags

No Cargo features are defined: every capability is unconditional, so no consumer can receive a half-wired crate.

Targets

KindNameSource
libapplication_encounters`src/lib.rs`
testpg_forge_encounters`tests/pg_forge_encounters.rs`

Error model

No public error type was detected: no public item declares a type named *Error, and no public signature returns one.

Operational characteristics

PropertyEvidence
async public surfaceyes
async runtimenone detected
database accessyes
network I/Onone detected
unsafe codenone detected
environment variablesyes

No unsafe block, unsafe fn, unsafe impl or unsafe trait was found by the parser anywhere in this crate's source.

Configuration

VariableRead in
CARGO_PKG_VERSIONsrc/lib.rs

No workspace crate depends on this one.

Verification

KindCount
Unit tests1
Integration tests1
Examples0
Doctests0

Evidence by module. How often each public module is named by something executable.

ModuleTestsExamplesConsumers
crate root100

What the tests establish, by name:

Documentation coverage

MeasureDocumentedTotal
Public items with rustdoc06
Public modules with a //! block00
pie showData
    title Public items with rustdoc
    "Documented" : 0
    "No rustdoc detected" : 6

Metrics

MetricValue
Rust source files1
Source lines99
Code lines62
Public API items6
Public modules0
Tests2
Examples0
Cargo features0
Direct runtime dependencies4
Workspace reverse dependencies0
pie showData
    title Public API by kind
    "method" : 5
    "struct" : 1
pie showData
    title Rust source composition
    "Code" : 62
    "Blank or comment" : 37

Generation

Rendered by tools-corpus corpus readme from repository evidence alone, renderer schema 2, lexicon current. No model, network service or database was consulted. Regenerate with tools-corpus corpus readme --write; verify with --check.

All application · Manual