Scope and limitations¶
This documentation describes the behavior implemented on the current frontend-derived code line. It does not claim that the prototype is an accredited government production service.
Supported workflow templates¶
The checked-in catalog currently focuses on:
- post-marriage government-record updates;
- direct government-record information updates.
The architecture supports additional versioned templates, but a newly imagined journey is not automatically authoritative. Questions, documents, agency responsibilities, and submission rules require validation.
What the prototype does¶
- captures and classifies citizen requests;
- keeps ambiguous conversation in chat;
- prepares a reviewable intent assessment;
- creates structured local journeys for supported requests;
- persists milestone, answer, and document state;
- manages private document metadata and upload paths;
- integrates with configured identity and AI provider adapters.
What it does not guarantee¶
- final acceptance by an agency;
- legal completeness of every requirement;
- automatic mutation of a government system of record;
- production-grade identity accreditation;
- permanent availability of hackathon sandbox providers;
- universal coverage of Philippine government services;
- safe operation without the production controls listed below.
Known technical limitations¶
| Area | Current limitation |
|---|---|
| Agent API | Authentication and ownership dependencies are not consistently applied; this is a production blocker. |
| Workflow catalog | The seed set is intentionally small and requires agency review. |
| Database operations | Local development favors SQLite and startup compatibility; production needs managed migrations and rollback procedures. |
| Documents | Upload protection still needs production malware scanning, retention, and deletion policies. |
| Provider sandboxes | Codes, tokens, and sessions may be short-lived, single-use, rate-limited, or unavailable. |
| Legacy code | Some older route/repository modules remain in the tree but are not mounted in the current API. |
| Operations | The repository does not include a complete production platform, monitoring stack, or incident runbook. |
Restricted integration material¶
Detailed eGovPH and eVerify partner specifications are made available through authorized channels. They may contain non-public endpoints, credential requirements, or operational constraints. eAkto documentation therefore records only:
- eAkto-owned endpoints and data boundaries;
- public configuration variable names;
- high-level flow and security responsibilities;
- links or references appropriate for authorized developers.
It does not reproduce private specifications, examples containing live identifiers, or any credential value.