Actionist Industry Registry
← Back to industry registry
law_firms · evidence-backed demand prior · observed 2026-08-27

Law Firms

Law firm demand centers on client intake, conflict checks, document drafting and billing admin; privilege classification constrains every data flow including discovery itself.

47Observed repo slots
8Distinct repos
4Observed demand cells
6Open matrix cells

Demand atoms and workflow

High-value read-only workflow

Read-only matter-intake desk: join intake fields, conflict-search results, document index, and billing-age views; identify missing review evidence.

Demand signal / validated demand

E — Catalogue signal: Handle client intake, conflict checks, document drafts, and billing administration.

U — Not established in this lane; no attributable industry denominator or repeated accepted-outcome receipt.

Atom join

intake_normalizetriage_routeextract_structureapproval_publishfollow_up_chase

Specification crosswalk: I — intake_normalize, triage_route, extract_structure, approval_publish, follow_up_chase

Industry model

Entities

prospective_clientmatterpartyconflict_hitdocumentattorneyinvoiceprivilege_classexception

States

received → normalized → conflict_pending → lawyer_review → cleared | hold; billing: open → aged → review

Terminal owner

responsible_lawyer_or_conflicts_manager

Authority boundary

Read-only synthetic matter and document metadata; no legal advice, conflict clearance, filing, draft release, billing write, or client contact.

Source of truth / exception paths

Source of truth: Practice-management/matter system plus document-management and billing ledgers; lawyer remains authoritative.

Exception paths: name collision; privileged content; conflict false positive; document version ambiguity; limitation/deadline; access denial

Discovery preparation

Precomputable context

  • matter/intake/conflict state machines
  • practice-management system vocabulary
  • privilege boundary (discovery may only touch metadata)
  • archetype fit (case/workflow + intake desk)

Questions that must be asked

  • PMS/DMS/billing systems and matter numbering authority
  • practice-area mix (drives entity variants)
  • conflict-check process reality
  • intake volume and conversion economics

Contradiction risks

  • intake speed wanted vs conflict-check rigor required
  • billing aging blamed on clients vs internal WIP release

Observed repository matrix

These are the non-null rows from repo-matrix-observations.jsonl for this industry. The 1,000-row partition includes reserved cells; only 47 observed repository slots are shown here.

RepositoryObserved slotsDimensionsCapability familiesObserved atoms
kartikbansalx/LegalVault-Legal-Document-Management-System ↗9agent_authority, data_model, demand_atom_fit, economics_maintenance, integration_surface, provenance_rights, runtime_deployment, ui_assembly, workflow_behaviordataapproval_publish, extract_structure, follow_up_chase, intake_normalize
AishwaryaSingh123/Court_and_Legal_Management_Systerm ↗8agent_authority, data_model, demand_atom_fit, economics_maintenance, integration_surface, provenance_rights, runtime_deployment, workflow_behaviordataapproval_publish, extract_structure, follow_up_chase, intake_normalize
stevenmcsorley/Private-Legal-DMS ↗8agent_authority, data_model, demand_atom_fit, economics_maintenance, provenance_rights, runtime_deployment, ui_assembly, workflow_behaviordataapproval_publish, extract_structure, follow_up_chase, intake_normalize
ELIOTT-BONTE/Legal_doc_processing_pipeline ↗6data_model, demand_atom_fit, economics_maintenance, provenance_rights, runtime_deployment, workflow_behaviordataapproval_publish, extract_structure, follow_up_chase, intake_normalize
webapplegal/webapplegal.github.io ↗5data_model, demand_atom_fit, economics_maintenance, runtime_deployment, workflow_behaviordataapproval_publish, extract_structure, follow_up_chase, intake_normalize
Michealvijayanelson/Online-legal-documentation ↗4data_model, demand_atom_fit, economics_maintenance, workflow_behaviordataapproval_publish, extract_structure, follow_up_chase, intake_normalize
xxminxx/paodocs ↗4data_model, demand_atom_fit, economics_maintenance, workflow_behaviordataapproval_publish, extract_structure, follow_up_chase, intake_normalize
Michealvijayanelson/Online-Legal-document-Management-System ↗3data_model, demand_atom_fit, economics_maintenancedataapproval_publish, extract_structure, follow_up_chase, intake_normalize

Empty-cell gap matrix

The ten category cells retain both demand and supply state. NO_OBSERVED_DEMAND_SIGNAL means the research denominator is empty; it is not a claim that the workflow does not exist.

Category / empty-cell keyObserved demandCandidate coverageSearch waveCandidate examples
Intake and normalizationintake_and_normalizationOBSERVED47 slots · 8 reposSHARED_CANDIDATE_COVERAGE10 candidate repos · 10 source rowsNOT_SEARCHEDno targeted search proposalLimeSurvey/LimeSurvey, ProcessMaker/processmaker, al1abb/invoify, formbricks/formbricks
Triage and routingtriage_and_routingNOT_OBSERVED_IN_750_SLOTS0 slots · 0 reposNO_OBSERVED_DEMAND_SIGNAL31 candidate repos · 31 source rowsNOT_SEARCHEDno targeted search proposalAlfresco/alfresco-community-repo, Leantime/leantime, ProcessMaker/processmaker, Worklenz/worklenz
Records, extraction and auditrecords_and_auditOBSERVED47 slots · 8 reposSHARED_CANDIDATE_COVERAGE47 candidate repos · 47 source rowsNOT_SEARCHEDno targeted search proposalAlfresco/alfresco-community-repo, AppFlowy-IO/AppFlowy, BookStackApp/BookStack, BuilderIO/builder
Classification and prioritizationclassification_and_prioritizationNOT_OBSERVED_IN_750_SLOTS0 slots · 0 reposNO_OBSERVED_DEMAND_SIGNAL39 candidate repos · 39 source rowsNOT_SEARCHEDno targeted search proposalDolibarr/dolibarr, PostHog/posthog, SuiteCRM/SuiteCRM, apache/superset
Scheduling and coordinationscheduling_and_coordinationNOT_OBSERVED_IN_750_SLOTS0 slots · 0 reposNO_OBSERVED_DEMAND_SIGNAL14 candidate repos · 14 source rowsNOT_SEARCHEDno targeted search proposalcalcom/cal.diy, alextselegidis/easyappointments, lukevella/rallly, thunderbird/appointment
Follow-up and communicationfollow_up_and_communicationOBSERVED47 slots · 8 reposSHARED_CANDIDATE_COVERAGE23 candidate repos · 23 source rowsNOT_SEARCHEDno targeted search proposalRocketChat/Rocket.Chat, TryGhost/Ghost, activepieces/activepieces, chatwoot/chatwoot
Reporting and digestreporting_and_digestNOT_OBSERVED_IN_750_SLOTS0 slots · 0 reposNO_OBSERVED_DEMAND_SIGNAL15 candidate repos · 15 source rowsNOT_SEARCHEDno targeted search proposalPostHog/posthog, apache/superset, bigcapitalhq/bigcapital, cube-js/cube
Monitoring and alertsmonitoring_and_alertsNOT_OBSERVED_IN_750_SLOTS0 slots · 0 reposNO_OBSERVED_DEMAND_SIGNAL0 candidate repos · 0 source rowsNOT_SEARCHEDno targeted search proposalnone recorded
Approval and controlled publishingapproval_and_controlled_publishOBSERVED47 slots · 8 reposSHARED_CANDIDATE_COVERAGE21 candidate repos · 21 source rowsNOT_SEARCHEDno targeted search proposalBudibase/budibase, ProcessMaker/processmaker, activepieces/activepieces, apache/airflow
Sync and browser operationssync_and_browser_operationsNOT_OBSERVED_IN_750_SLOTS0 slots · 0 reposNO_OBSERVED_DEMAND_SIGNAL1 candidate repos · 1 source rowsNOT_SEARCHEDno targeted search proposalactivepieces/activepieces

Shelf candidates joined to this industry

These records come from the permanent source registry's industry-demand join. A joined candidate remains a discovery/research record; qualification and admission are shown explicitly.

Joined shelf recordObserved slotsFamilies / atomsCurrent verdictQualification / admission
AishwaryaSingh123/Court_and_Legal_Management_Systerm ↗8dataapproval_publish, extract_structure, follow_up_chase, intake_normalizediscovery_candidateNOT_QUALIFIED / NOT_ADMITTED
ELIOTT-BONTE/Legal_doc_processing_pipeline ↗6dataapproval_publish, extract_structure, follow_up_chase, intake_normalizediscovery_candidateNOT_QUALIFIED / NOT_ADMITTED
kartikbansalx/LegalVault-Legal-Document-Management-System ↗9dataapproval_publish, extract_structure, follow_up_chase, intake_normalizediscovery_candidateNOT_QUALIFIED / NOT_ADMITTED
Michealvijayanelson/Online-Legal-document-Management-System ↗3dataapproval_publish, extract_structure, follow_up_chase, intake_normalizediscovery_candidateNOT_QUALIFIED / NOT_ADMITTED
Michealvijayanelson/Online-legal-documentation ↗4dataapproval_publish, extract_structure, follow_up_chase, intake_normalizediscovery_candidateNOT_QUALIFIED / NOT_ADMITTED
stevenmcsorley/Private-Legal-DMS ↗8dataapproval_publish, extract_structure, follow_up_chase, intake_normalizediscovery_candidateNOT_QUALIFIED / NOT_ADMITTED
webapplegal/webapplegal.github.io ↗5dataapproval_publish, extract_structure, follow_up_chase, intake_normalizediscovery_candidateNOT_QUALIFIED / NOT_ADMITTED
xxminxx/paodocs ↗4dataapproval_publish, extract_structure, follow_up_chase, intake_normalizediscovery_candidateNOT_QUALIFIED / NOT_ADMITTED

Open gaps

Triage and routing

NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 31 candidate repositories.

NOT_SEARCHED. Exact P03 workflow/support/project kinds; a product README alone is not semantic coverage.

Classification and prioritization

NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 39 candidate repositories.

NOT_SEARCHED. Exact P03 CRM/analytics/search candidates are adjacent supply, not proof of a classifier workflow.

Scheduling and coordination

NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 14 candidate repositories.

NOT_SEARCHED. Exact P03 scheduling kind only; calendar UI alone is not a booking/authority proof.

Reporting and digest

NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 15 candidate repositories.

NOT_SEARCHED. Exact P03 analytics kind; a reporting surface is not a measured client outcome.

Monitoring and alerts

NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 0 candidate repositories.

NOT_SEARCHED. No dedicated P03 capability kind is mapped; analytics is not silently promoted to monitoring.

Sync and browser operations

NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 1 candidate repositories.

NOT_SEARCHED. Connector candidates cover a possible sync seam; no direct P03 browser-operation kind is available.

Safe-pilot boundary

Rationale

Metadata-only, synthetic intake supports evidence-boundary testing while preserving privilege and lawyer approval.

Falsifier

A held-out conflict/document fixture cannot preserve privilege and version identity, or any outcome depends on legal judgment or external filing.

Sources: research/actionmodel-builder-research-2026-08-26/phase-2/outputs/industry-atom-specifications.md · research/workstreams/p01-client-intelligence/runs/2026-08-27-sprint-1-fable/industry-discovery-priors.jsonl · research/actionmodel-builder-research-2026-08-26/expansion/outputs/repo-matrix-observations.jsonl · research/workstreams/2026-08-28-program-driver/shelf-prebake/industry-gap-matrix.json · knowledge/capability-shelf/source-registry.jsonl