GovOPlaN/govoplan-forms-runtime
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

[Feature] Implement definition-aware Forms Runtime and Service launcher #1

New Issue
Closed
opened 2026-08-01 14:53:10 +02:00 by zemion · 2 comments
zemion commented 2026-08-01 14:53:10 +02:00
Owner
Copy Link
Copy Source

Outcome

Implement the definition-aware Forms Runtime vertical required to launch a form-bound institutional Service without weakening validation, tenant isolation, provenance, or recovery guarantees.

Acceptance criteria

  • Resolve one immutable form definition and exact revision through a provider-neutral Forms capability.
  • Persist tenant-bound draft/submission identities, immutable status history, validation results, attachment/signature references, and case/workflow/record/evidence handoffs.
  • Validate schema, policy, and current access on the server before draft persistence and final submission.
  • Make create/retry replay-safe and draft updates optimistic-concurrency guarded.
  • Provide bounded APIs and an accessible runtime WebUI without importing Forms, Files, Cases, Workflow, or Portal tables.
  • Provide forms_runtime.service_launcher using Core ServiceLaunchRequest/ServiceLaunchResult, retaining the exact Service and binding and returning a same-tenant submission target.
  • Add migrations, uninstall guards, permissions, committed events/audit context, recovery documentation, and tests for tenant isolation, stale writes, replay conflicts, invalid definitions, and failed handoffs.
  • Keep Portal form entries explainably unavailable until the launcher and its required definition provider are active.

Boundary

Forms owns immutable definitions and authoring. Forms Runtime owns instances and submissions. Portal owns discovery and launch delegation. Domain modules own adjudication and handoff targets. A placeholder that accepts arbitrary fields without resolving and validating a definition is not acceptable.

Reference: govoplan/docs/INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md and govoplan-forms-runtime/docs/FORMS_RUNTIME_DOMAIN_BOUNDARY.md.

## Outcome Implement the definition-aware Forms Runtime vertical required to launch a form-bound institutional Service without weakening validation, tenant isolation, provenance, or recovery guarantees. ## Acceptance criteria - Resolve one immutable form definition and exact revision through a provider-neutral Forms capability. - Persist tenant-bound draft/submission identities, immutable status history, validation results, attachment/signature references, and case/workflow/record/evidence handoffs. - Validate schema, policy, and current access on the server before draft persistence and final submission. - Make create/retry replay-safe and draft updates optimistic-concurrency guarded. - Provide bounded APIs and an accessible runtime WebUI without importing Forms, Files, Cases, Workflow, or Portal tables. - Provide `forms_runtime.service_launcher` using Core `ServiceLaunchRequest`/`ServiceLaunchResult`, retaining the exact Service and binding and returning a same-tenant submission target. - Add migrations, uninstall guards, permissions, committed events/audit context, recovery documentation, and tests for tenant isolation, stale writes, replay conflicts, invalid definitions, and failed handoffs. - Keep Portal form entries explainably unavailable until the launcher and its required definition provider are active. ## Boundary Forms owns immutable definitions and authoring. Forms Runtime owns instances and submissions. Portal owns discovery and launch delegation. Domain modules own adjudication and handoff targets. A placeholder that accepts arbitrary fields without resolving and validating a definition is not acceptable. Reference: `govoplan/docs/INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md` and `govoplan-forms-runtime/docs/FORMS_RUNTIME_DOMAIN_BOUNDARY.md`.
zemion commented 2026-08-01 16:28:44 +02:00
Author
Owner
Copy Link
Copy Source

Codex State: progress

Summary

  • Implemented definition-aware drafts/submissions, exact Service/Form provenance, validation, receipts, status history, handoff evidence, APIs, permissions, migrations, and accessible runtime WebUI.
  • Added forms_runtime.service_launcher and an executable Portal to exact Form revision journey.
  • Hardened replay so keys are actor-bound, exact retries survive schema supersession, mismatched providers fail closed, and client IDs cannot replace existing state.

Verification

  • 8 Forms Runtime tests pass, including fresh migrations and security regressions
  • Isolated access+portal+forms+forms_runtime startup smoke passes
  • 42 WebUI module permutations pass

Next / Blocked

  • Push the source changes, then close this issue.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Implemented definition-aware drafts/submissions, exact Service/Form provenance, validation, receipts, status history, handoff evidence, APIs, permissions, migrations, and accessible runtime WebUI. - Added forms_runtime.service_launcher and an executable Portal to exact Form revision journey. - Hardened replay so keys are actor-bound, exact retries survive schema supersession, mismatched providers fail closed, and client IDs cannot replace existing state. ### Verification - `8 Forms Runtime tests pass, including fresh migrations and security regressions` - `Isolated access+portal+forms+forms_runtime startup smoke passes` - `42 WebUI module permutations pass` ### Next / Blocked - Push the source changes, then close this issue. Suggested status label: `status/in-progress`
zemion added
status
in-progress
 and removed
status
ready
 labels 2026-08-01 16:30:18 +02:00
zemion commented 2026-08-01 17:50:23 +02:00
Author
Owner
Copy Link
Copy Source

Codex State: done

The verified implementation has been committed and pushed on main in 9dc49fe. The issue acceptance scope is complete; follow-on product depth remains tracked separately.

## Codex State: done The verified implementation has been committed and pushed on `main` in `9dc49fe`. The issue acceptance scope is complete; follow-on product depth remains tracked separately.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
HTTP API contracts, routers, schemas, or API smoke behavior.
 area/auth
Authentication, sessions, access bootstrap, or login behavior.
 area/db
Database sessions, models, transactions, or persistence primitives.
 area/devex
Local developer workflow, scripts, tests, tooling, or release helpers.
 area/docs
Durable documentation and project guidance.
 area/governance
Governance policy, audit, privacy, retention, or compliance behavior.
 area/marketing
Public website, product messaging, publication copy, or legal page content.
 area/migrations
Alembic migrations, schema bootstrap, or persistence evolution.
 area/module-system
Module discovery, manifests, capabilities, routing, or optional integrations.
 area/rbac
Permissions, roles, delegation, or authorization policy.
 area/release
Versioning, release locks, tags, packaging, or dependency pins.
 area/security
Security posture, static analysis, supply-chain hardening, or vulnerability remediation.
 area/tenancy
Tenant boundaries, provisioning, or tenant-scoped data behavior.
 area/webui
Shared WebUI shell, frontend components, routing, or frontend tests.
 audit/complexity
Complexity finding from Radon, Xenon, or equivalent maintainability scans.
 audit/duplication
Duplicated-code finding from jscpd or equivalent similarity scans.
 audit/false-positive
Audit finding reviewed as a narrow false positive or acceptable risk.
 audit/needs-design
Audit finding that needs an architectural or product decision before implementation.
 audit/quick-fix
Audit finding that appears narrow and directly fixable.
 audit/structural
Audit finding that needs design, refactoring, or behavior review.
 codex/needs-human
Needs an explicit human decision before Codex should implement.
 codex/ready
Suitable for Codex to pick up with the existing issue context.
 module/access
GovOPlaN access, identity, authentication, RBAC, and administration behavior.
 module/addresses
GovOPlaN Addresses module behavior or integration.
 module/admin
GovOPlaN Admin module behavior or integration.
 module/appointments
GovOPlaN Appointments module behavior or integration.
 module/approvals
GovOPlaN Approvals module behavior or integration.
 module/audit
GovOPlaN Audit module behavior or integration.
 module/calendar
GovOPlaN Calendar module behavior or integration.
 module/campaign
GovOPlaN campaign module behavior or integration.
 module/cases
GovOPlaN Cases module behavior or integration.
 module/committee
GovOPlaN Committee module behavior or integration.
 module/connectors
GovOPlaN Connectors module behavior or integration.
 module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
 module/dashboard
GovOPlaN Dashboard module behavior or integration.
 module/dataflow
GovOPlaN Dataflow module behavior or integration.
 module/datasources
GovOPlaN governed datasource contracts, catalogs, and integrations.
 module/decisions
GovOPlaN formal Decisions module behavior or integration.
 module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
 module/dms
GovOPlaN Dms module behavior or integration.
 module/docs
GovOPlaN Docs module behavior or integration.
 module/encryption
GovOPlaN Encryption key custody, cryptographic policy, and E2EE integration.
 module/erp
GovOPlaN Erp module behavior or integration.
 module/evaluation
GovOPlaN Evaluation module behavior or integration.
 module/files
GovOPlaN files module behavior or integration.
 module/fit-connect
GovOPlaN Fit Connect module behavior or integration.
 module/forms
GovOPlaN Forms module behavior or integration.
 module/forms-runtime
GovOPlaN Forms Runtime module behavior or integration.
 module/helpdesk
GovOPlaN Helpdesk module behavior or integration.
 module/identity
GovOPlaN Identity module behavior or integration.
 module/identity-trust
GovOPlaN Identity Trust module behavior or integration.
 module/idm
GovOPlaN Idm module behavior or integration.
 module/ledger
GovOPlaN Ledger module behavior or integration.
 module/mail
GovOPlaN mail module behavior or integration.
 module/mandates
GovOPlaN Mandates, jurisdiction, responsibility, and authority behavior or integration.
 module/notifications
GovOPlaN Notifications module behavior or integration.
 module/ops
GovOPlaN Ops module behavior or integration.
 module/organizations
GovOPlaN Organizations module behavior or integration.
 module/parties
GovOPlaN procedure Parties, representation, and delivery-authority behavior or integration.
 module/payments
GovOPlaN Payments module behavior or integration.
 module/permits
GovOPlaN Permits module behavior or integration.
 module/policy
GovOPlaN Policy module behavior or integration.
 module/poll
GovOPlaN Poll module behavior or integration.
 module/portal
GovOPlaN Portal module behavior or integration.
 module/postbox
GovOPlaN Postbox module behavior or integration.
 module/projects
GovOPlaN Projects module behavior or integration.
 module/reporting
GovOPlaN Reporting module behavior or integration.
 module/risk-compliance
GovOPlaN Risk Compliance module behavior or integration.
 module/scheduling
GovOPlaN Scheduling module behavior or integration.
 module/search
GovOPlaN Search module behavior or integration.
 module/services
GovOPlaN versioned institutional Services behavior or integration.
 module/tasks
GovOPlaN Tasks module behavior or integration.
 module/templates
GovOPlaN Templates module behavior or integration.
 module/tenancy
GovOPlaN Tenancy module behavior or integration.
 module/tickets
GovOPlaN Tickets module behavior or integration.
 module/views
GovOPlaN governed task views, interface projections, and workflow view integration.
 module/wiki
GovOPlaN Wiki module behavior or integration.
 module/workflow
GovOPlaN Workflow module behavior or integration.
 module/workflow-engine
GovOPlaN Workflow Engine runtime, persistence, or integration.
 module/xoev
GovOPlaN Xoev module behavior or integration.
 module/xrechnung
GovOPlaN Xrechnung module behavior or integration.
 module/xta-osci
GovOPlaN Xta Osci module behavior or integration.
priority
p0
Immediate stop-the-line priority.
priority
p1
High priority for the next focused work window.
priority
p2
Normal planned priority.
priority
p3
Low priority or opportunistic cleanup.
source/backlog-import
Imported from markdown backlog, roadmap, plan, or TODO files.
 source/security-audit
Created from a structured security or code-quality audit report.
 source/todo-scan
Imported from inline TODO/FIXME/HACK markers by the Gitea TODO importer.
status
blocked
Cannot progress without a decision, dependency, credential, or external change.
status
in-progress
Currently being worked.
status
needs-info
Needs clarifying input before implementation can proceed safely.
status
ready
Ready for implementation.
status
triage
Needs review, ownership, priority, or acceptance criteria.
type
bug
A reproducible defect, regression, or incorrect behavior.
type
debt
Cleanup, refactoring, risk reduction, or deferred engineering work.
type
docs
Documentation, process, or developer workflow work.
type
feature
New user-visible behavior or platform capability.
type
task
Implementation, maintenance, migration, or operational work.
type
user-story
End-to-end user journey or real-world process story used to steer product slices.
No labels area/api area/db area/security area/webui codex/ready module/forms-runtime
priority
p1
status
in-progress
type
feature
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
zemion
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-forms-runtime#1