Developers

Developer-facing reference for Fund Analyst Intelligence: architecture, data model, APIs, and production operations.

Developers

This section is for engineering teams integrating or operating Fund Analyst Intelligence in production.
It focuses on stable contracts, deterministic workflows, and operational reliability.
It is written for platform owners, integration engineers, and DevOps teams.

Fund Analyst Intelligence is not a single feature.
It is a pipeline with governance surfaces.
Engineering success depends on treating it as a system.

What you will find here

Architecture

How the system is structured and how major components interact.

Read: Architecture

Data model

The canonical entities used to represent funds, artefacts, claims, cycles, and snapshots.

Read: Data model

APIs

The stable interfaces used by the UI and partner systems.
Includes core endpoints and contract design principles.

Read: APIs

Deployments

Production operations, environments, and release discipline.

Read: Deployments

Design expectations

Deterministic core

Validation and delta computation should be reproducible.
Core logic should be testable and versioned.
Outputs should not depend on hidden state.

Evidence-first

Evidence links are part of the contract.
Data without provenance is not acceptable for production reporting.
Integrations should preserve versioning and timestamps.

Explicit workflow states

Draft, review, approved, and published are not UI concepts.
They are operational states that govern output release.
APIs should enforce these states.

Observability

Cycle runs should be visible and diagnosable.
Failures should be classified and actionable.
Reruns should be controlled and auditable.

Next step

If you are integrating, start with the Architecture and Data model.
If you are operating the system, go directly to Deployments.