Organize research library and schemas

papers/finance-automation/automated-finance-architecture.md

@@ -0,0 +1,26 @@
+# Automated Finance Architecture
+
+BlackRoad OS models finance automation through orchestrated agents that mirror traditional corporate finance controls while remaining auditable via PS-SHA∞ journaling. The architecture centers on eight core finance agents coordinated by a finance orchestrator and exposed through API and Prism views.
+
+## Core Components
+
+- **Finance orchestrator:** Routes tasks, enforces segregation of duties, and coordinates PS-SHA∞ logging.
+- **Core agents:** Close, treasury, FP&A, procurement, compliance, tax, reporting, and controls agents handle domain-specific actions.
+- **API + Prism views:** External interfaces for ingesting events, triggering workflows, and surfacing journaled outcomes.
+
+## Reference Foundations
+
+- **Corporate finance literature:** Valuation, risk, and capital structure concepts from Brealey and OpenStax guide agent policies and scenario modeling.
+- **Regulatory expectations:** FINRA/SEC focuses on suitability, surveillance, and market integrity influence orchestration rules.
+- **Automation handbooks:** Industrial automation patterns inform safety constraints, redundancy, and recovery strategies.
+
+## PS-SHA∞ Integration
+
+- Every financial action is journaled with hashes and prior links to preserve an auditable worldline.
+- Contradictions between agents (e.g., revenue vs. compliance) are recorded with resolution metadata.
+- Journal entries can be exported for external attestations or compliance tooling.
+
+## TODOs
+
+- Elaborate data contracts for each agent API and align with `schemas/journal-entry.schema.json`.
+- Prototype scenario simulations to stress-test segregation-of-duties policies.

papers/finance-automation/regulated-industry-considerations.md

@@ -0,0 +1,23 @@
+# Regulated Industry Considerations
+
+The finance automation vision is conceptual and aspirational; it is not a claim of compliance. The design aims to align with GAAP/IFRS expectations and regulatory frameworks such as FINRA and SEC while preserving flexibility for jurisdictional variation.
+
+## Accounting Alignment
+
+- **GAAP/IFRS hooks:** Journal entry structures can map to ledger postings and disclosures, supporting external reporting pipelines.
+- **Controls:** Segregation of duties and PS-SHA∞ journaling provide traceability for approvals and policy overrides.
+
+## Regulatory Overlays
+
+- **FINRA/SEC:** Suitability, best execution, market surveillance, and recordkeeping requirements inform orchestration rules and logging depth.
+- **AML/KYC:** Agents should integrate identity verification and suspicious activity patterns, with contradictions escalated when risk flags collide with revenue objectives.
+
+## Posture Statement
+
+- **Conceptual only:** These documents describe intended capabilities, not audited compliance states.
+- **Evidence-ready:** The combination of journaled actions and explicit contradiction handling is designed to support future attestations.
+
+## TODOs
+
+- Map specific regulatory controls to agent responsibilities and PS-SHA∞ fields.
+- Draft sample audit trails demonstrating how finance workflows surface and resolve conflicts.