application-communication

Forge module: generic per-firm communications timeline (record plane over any channel — whatsapp/sms/email/call/letter/filing/note), matter-optional, with participants + rebuttals. Distinct from infrastructure-communication's live outbound-messaging plane, which it re-exports.

Tier	application
Role	unclassified (baselined)
Path	`crates/application/communication`
Edition	2024
Targets	application_communication, live_db
Public items	7 across 0 modules
Tests	1

What it is for

application-communication — the generic, per-firm communications timeline plane.

Two distinct things share the word "communication" in Forge:

infrastructure_communication (re-exported below) is the LIVE outbound-messaging

plane — ChatMessage, channel senders, outbound workers.

THIS module is the RECORD/timeline plane: a firm-scoped, matter-optional

communications table that captures anything said or sent — whatsapp, sms, email, call, voicemail, letter, statement, police_report, filing, note — whether live-captured, imported from a legacy system, or transcribed.

It is deliberately generic: no legal/case ETL, no case-forge coupling. Any app that needs "one timeline of everything" composes the schema (migrations/), persistence (repo), and the mountable firm_router. Locked semantics: assertion (content epistemics) and verified (human review) are independent axes; occurred_at + occurred_precision is the only event-time.

Capabilities

`CommunicationModule`

application-communication — the generic, per-firm communications timeline plane.

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

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`

Item	What it is
`pub struct CommunicationModule`	The mountable Forge module: owns the `communications` schema + permissions.
`CommunicationModule :: fn new() -> Self`	Construct the module.
`CommunicationModule :: fn name(& self) -> & 'static str`	—
`CommunicationModule :: fn version(& self) -> & 'static str`	—
`CommunicationModule :: fn migrations(& self) -> Vec <MigrationSet>`	—
`CommunicationModule :: async fn migrate_pending(& self, pool : & PgPool) -> Result <u32, MigrationError>`	—
`CommunicationModule :: fn permission_codes(& self) -> Vec <String>`	—

Re-exports. Exported here, defined elsewhere.

Export	Defined in
`ServiceError`	`error::ServiceError`
`firm_router`	`api::firm_router`
`{Communication,NewCommunication,NewParticipant,NewRebuttal,add_participant,add_rebuttal,get_communication,insert_communication,list_by_matter,}`	`repo::{Communication,NewCommunication,NewParticipant,NewRebuttal,add_participant,add_rebuttal,get_communication,insert_communication,list_by_matter,}`

Boundary

Reaches into infrastructure.

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)`
Location	`crates/application/communication`
Vocabulary in force (lexicon)	`current`

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

flowchart LR
  n_application["application"] --> n_infrastructure["infrastructure"]

Dependencies

Runtime, in this workspace.

Crate	Tier	Optional	Only on
`application-core`	application	no	always
`infrastructure-communication`	infrastructure	no	always
`infrastructure-tenant-pool`	infrastructure	no	always

Runtime, from outside the workspace.

Crate	Requirement	Features	Optional	Only on
`async-trait`	`^0.1`	—	no	always
`axum`	`^0.7`	`multipart`	no	always
`chrono`	`^0.4`	`serde`, `serde`	no	always
`serde`	`^1`	`derive`, `derive`	no	always
`serde_json`	`^1`	—	no	always
`sqlx`	`^0.8`	`runtime-tokio`, `postgres`, `chrono`, `uuid`, `json`, `migrate`	no	always
`thiserror`	`^2`	—	no	always
`uuid`	`^1`	`v4`, `v7`, `serde`, `js`, `v4`, `serde`	no	always

Development, from outside the workspace.

Crate	Requirement	Features	Optional	Only on
`tokio`	`^1`	`full`, `macros`, `rt-multi-thread`	no	always

Build. None.

Depended on by. Nothing in this workspace.

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

flowchart LR
  SELF["application-communication"]
  SELF -->|runtime| n_application_core["application-core"]
  SELF -->|runtime| n_infrastructure_communication["infrastructure-communication"]
  SELF -->|runtime| n_infrastructure_tenant_pool["infrastructure-tenant-pool"]
  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

Kind	Name	Source
lib	`application_communication`	`src/lib.rs`
test	`live_db`	`tests/live_db.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

Property	Evidence
async public surface	yes
async runtime	none detected
database access	yes
network I/O	yes
unsafe code	none detected
environment variables	yes

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

Configuration

Variable	Read in
`CARGO_PKG_VERSION`	`src/lib.rs`

No workspace crate depends on this one.

Verification

Kind	Count
Unit tests	0
Integration tests	1
Examples	0
Doctests	0

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

Module	Tests	Examples	Consumers
`crate root`	1	0	0

What the tests establish, by name:

timeline_insert_participants_rebuttal_and_import_idempotency — tests/live_db.rs

Documentation coverage

Measure	Documented	Total
Public items with rustdoc	2	7
Public modules with a `//!` block	0	0

pie showData
    title Public items with rustdoc
    "Documented" : 2
    "No rustdoc detected" : 5

Metrics

Metric	Value
Rust source files	4
Source lines	646
Code lines	467
Public API items	7
Public modules	0
Tests	1
Examples	0
Cargo features	0
Direct runtime dependencies	11
Workspace reverse dependencies	0

pie showData
    title Public API by kind
    "method" : 6
    "struct" : 1

pie showData
    title Rust source composition
    "Code" : 467
    "Blank or comment" : 179

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.