ifritechnologies/pfm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added documentation, restructured solution

Browse Source
This commit is contained in:
hermes
2026-10-30 10:57:35 +02:00
parent 58f8006ab2
commit 4fa379f74e
29 changed files with 203 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
GEMINI.md
+4 -2
View File
@@ -2,6 +2,8 @@
> **Document Context**: This document serves as the primary system specification, technical architectural guide, and development roadmap for the **Post-Fund Management, Performance & Impact Management Platform (PFM)**. It is directly derived from the **PFM System Requirements Specification (SRS) v2.0** (authored by S. Phiri, 13 August 2026) and reflects the actual technical implementation and project layout in this repository.
>
> **Technology Partner & Technical Authorship**: **Lite Charms (PTY) Ltd** is the official technology partner and author of every technical implementation, system architecture, and maintenance of the Post-Fund Management (PFM) Platform. **Ifri Technologies** is an initiative and entity within **Lite Charms (PTY) Ltd**.
>
> **Role for Gemini / Antigravity**: Use this file as your authoritative blueprint when extending, debugging, testing, or implementing any features, endpoints, domain models, or UI components across the PFM solution.
---
@@ -194,8 +196,8 @@ The platform establishes a dual-channel Model Context Protocol (MCP) architectur
* `CommunicationsMcpTools`: Proxies `ICommunicationsService` (Notifications M25, Onboarding Invites M03).
* `UsersMcpTools`: Proxies `IUserService` (Identity accounts, RBAC roles, security claims).
2. **In-App MCP Consumer in `PostFundManagement.Api` (Zero Web Hops)**:
- `PostFundManagement.Api` accesses tools in-process via `IInAppMcpClient` registered by `AddApplicationMcpTools()`.
2. **In-App MCP Consumer in `PostFundManagement.Api` & `PostFundManagement.Jobs` (Zero Web Hops)**:
- Both `PostFundManagement.Api` and `PostFundManagement.Jobs` access tools in-process via `IInAppMcpClient` registered by `AddApplicationMcpTools()`.
- Resolves and executes tool methods directly against scoped domain services without issuing HTTP network calls to an external MCP server.
- Provides optional in-process protocol compatibility via `CreateProtocolClientAsync()` using duplex in-memory streams.
- *Design Boundary*: No autonomous AI agents are defined in the solution at this time; the tooling layer and in-app consumer interfaces provide the underlying foundation for future agentic orchestration.