GovOPlaN/govoplan
1
0
Fork 0
Code Issues 10 Pull Requests Actions 3 Packages Projects Releases Wiki Activity

[User Story] Demonstrate the connected platform from Campaign through Postbox, data, BI, and collaborative documents #14

New Issue
Open
opened 2026-07-21 15:42:56 +02:00 by zemion · 3 comments
zemion commented 2026-07-21 15:42:56 +02:00
Owner
Copy Link

Outcome

As an institution evaluating and adopting GovOPlaN, I want a sequence of complete, connected reference journeys so that I can understand the product from user, process, administration, operation, integration, security, and audit perspectives and prove that independently installed modules form one trustworthy governance platform.

Selected sequence

  1. Campaign as the demonstration composition, with Mail-owned profiles, Files, target delivery/recovery, central UI, and adaptive Campaign/Mail/Files documentation.
  2. Postbox delivery to a function in an organizational unit through Organizations, Identity, IDM, and Access, including reassignment, delegation, vacancy, retention, and audit behavior.
  3. Templates and Reports over governed data sources, including a safe HIS-style deep launch to a prefilled, reproducible document/report task.
  4. One governed university source-to-indicator BI path with staging, validation, versioned transformations, official keys, lineage, policy-aware drill-down, and environment promotion.
  5. Collaborative document editing through DMS over Files, including versions, conflicts, review/approval, provider-neutral editing sessions, recovery, and Records handoff.

Workflow remains deferred and is not a dependency. Connector safety, typed capability contracts, provenance, external-effect handling, focused central-component UI, adaptive documentation, release alignment, recovery, and target acceptance form a continuous foundation lane.

Acceptance

  • Each stage is delivered as small reviewable increments and passes the explicit gate in the selected program document.
  • A pinned composition demonstrates the named end-to-end journey, its degraded states, and its operator recovery path.
  • Feature modules own canonical subject matter; Docs renders installed/configured/actor-aware perspectives without duplicating business rules.
  • Optional modules integrate only through versioned Core-mediated capabilities and typed references.
  • User-visible claims distinguish code-tested, target-tested, package-integrated, pilot-approved, and production-approved evidence.
  • Later stage tickets are decomposed only when the preceding contracts are sufficiently stable or the stage is explicitly activated.

Canonical direction

Existing Campaign and Postbox repository issues provide the current feature decomposition. This story owns cross-stage sequencing and gates, not module implementation details.

Activated Postbox stage

The Postbox stage is now decomposed under govoplan-postbox#16, including the IDM/Organizations foundations and Campaign channel adapter.

## Outcome As an institution evaluating and adopting GovOPlaN, I want a sequence of complete, connected reference journeys so that I can understand the product from user, process, administration, operation, integration, security, and audit perspectives and prove that independently installed modules form one trustworthy governance platform. ## Selected sequence 1. Campaign as the demonstration composition, with Mail-owned profiles, Files, target delivery/recovery, central UI, and adaptive Campaign/Mail/Files documentation. 2. Postbox delivery to a function in an organizational unit through Organizations, Identity, IDM, and Access, including reassignment, delegation, vacancy, retention, and audit behavior. 3. Templates and Reports over governed data sources, including a safe HIS-style deep launch to a prefilled, reproducible document/report task. 4. One governed university source-to-indicator BI path with staging, validation, versioned transformations, official keys, lineage, policy-aware drill-down, and environment promotion. 5. Collaborative document editing through DMS over Files, including versions, conflicts, review/approval, provider-neutral editing sessions, recovery, and Records handoff. Workflow remains deferred and is not a dependency. Connector safety, typed capability contracts, provenance, external-effect handling, focused central-component UI, adaptive documentation, release alignment, recovery, and target acceptance form a continuous foundation lane. ## Acceptance - Each stage is delivered as small reviewable increments and passes the explicit gate in the selected program document. - A pinned composition demonstrates the named end-to-end journey, its degraded states, and its operator recovery path. - Feature modules own canonical subject matter; Docs renders installed/configured/actor-aware perspectives without duplicating business rules. - Optional modules integrate only through versioned Core-mediated capabilities and typed references. - User-visible claims distinguish code-tested, target-tested, package-integrated, pilot-approved, and production-approved evidence. - Later stage tickets are decomposed only when the preceding contracts are sufficiently stable or the stage is explicitly activated. ## Canonical direction - [Reference Journey Program](https://git.add-ideas.de/add-ideas/govoplan/src/branch/main/docs/REFERENCE_JOURNEY_PROGRAM.md) - [Connected Governance Platform Roadmap](https://git.add-ideas.de/add-ideas/govoplan/src/branch/main/docs/CONNECTED_GOVERNANCE_PLATFORM_ROADMAP.md) Existing Campaign and Postbox repository issues provide the current feature decomposition. This story owns cross-stage sequencing and gates, not module implementation details. <!-- codex-postbox-story-link-2026-07-28 --> ## Activated Postbox stage The Postbox stage is now decomposed under [govoplan-postbox#16](https://git.add-ideas.de/GovOPlaN/govoplan-postbox/issues/16), including the IDM/Organizations foundations and Campaign channel adapter.
zemion commented 2026-07-22 15:38:50 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • Added a credential-free simple-announcement Campaign fixture and isolated validate/build acceptance path.
  • The fixture explicitly proves Campaign works without optional Files/Mail imports, network access, attachments, or inline credentials, and builds deterministic normalized EML twice.

Changed Files

  • /mnt/DATA/git/govoplan-campaign/examples/simple-announcement/campaign.json
  • /mnt/DATA/git/govoplan-campaign/examples/simple-announcement/fixture.json
  • /mnt/DATA/git/govoplan-campaign/tests/test_example_campaigns.py

Verification

  • Campaign focused backend checks: 36 passed; full suite: 182 passed; aggregate-report WebUI structure passed.

Next / Blocked

  • Keep open for the target SMTP/IMAP journey and later Postbox/data/BI/document stages.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Added a credential-free simple-announcement Campaign fixture and isolated validate/build acceptance path. - The fixture explicitly proves Campaign works without optional Files/Mail imports, network access, attachments, or inline credentials, and builds deterministic normalized EML twice. ### Changed Files - `/mnt/DATA/git/govoplan-campaign/examples/simple-announcement/campaign.json` - `/mnt/DATA/git/govoplan-campaign/examples/simple-announcement/fixture.json` - `/mnt/DATA/git/govoplan-campaign/tests/test_example_campaigns.py` ### Verification - `Campaign focused backend checks: 36 passed; full suite: 182 passed; aggregate-report WebUI structure passed.` ### Next / Blocked - Keep open for the target SMTP/IMAP journey and later Postbox/data/BI/document stages. Suggested status label: `status/in-progress`
zemion commented 2026-07-22 17:19:16 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • Added a credential-free Campaign reference journey that creates a Mail-owned encrypted profile, validates/builds one message, performs one explicit synchronous send and one IMAP append, and correlates Campaign report/audit evidence with GreenMail.
  • A repeated ordinary send is rejected before a second provider effect; evidence declares the full Core/Access/Audit/Campaign/Mail composition and explicitly does not claim source-artifact or institutional target approval.

Changed Files

  • govoplan-campaign/dev/mail-testbed/run_campaign_acceptance.py
  • govoplan-campaign/examples/greenmail-delivery

Verification

  • 197 Campaign tests passed; live GreenMail success journey and three failure drills passed

Next / Blocked

  • Institutional target-provider acceptance and the remaining ambiguity/restart drills are still required before Stage 1 is complete.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Added a credential-free Campaign reference journey that creates a Mail-owned encrypted profile, validates/builds one message, performs one explicit synchronous send and one IMAP append, and correlates Campaign report/audit evidence with GreenMail. - A repeated ordinary send is rejected before a second provider effect; evidence declares the full Core/Access/Audit/Campaign/Mail composition and explicitly does not claim source-artifact or institutional target approval. ### Changed Files - `govoplan-campaign/dev/mail-testbed/run_campaign_acceptance.py` - `govoplan-campaign/examples/greenmail-delivery` ### Verification - `197 Campaign tests passed; live GreenMail success journey and three failure drills passed` ### Next / Blocked - Institutional target-provider acceptance and the remaining ambiguity/restart drills are still required before Stage 1 is complete. Suggested status label: `status/in-progress`
zemion commented 2026-07-28 00:58:11 +02:00
Author
Owner
Copy Link

The Stage 4 governed source-to-indicator path now has an implementation foundation in GovOPlaN/govoplan-dataflow#1. Reporting consumption is tracked in GovOPlaN/govoplan-reporting#2. The canonical documentation links in this issue still use the former organization path and should resolve to GovOPlaN after the repository move.

The Stage 4 governed source-to-indicator path now has an implementation foundation in https://git.add-ideas.de/GovOPlaN/govoplan-dataflow/issues/1. Reporting consumption is tracked in https://git.add-ideas.de/GovOPlaN/govoplan-reporting/issues/2. The canonical documentation links in this issue still use the former organization path and should resolve to `GovOPlaN` after the repository move. <!-- codex-dataflow-stage-link-2026-07-28 -->
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/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/connectors
GovOPlaN Connectors module behavior or integration.
module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
module/dataflow
GovOPlaN Dataflow module behavior or integration.
module/datasources
GovOPlaN governed datasource contracts, catalogs, and integrations.
module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
module/dms
GovOPlaN Dms module behavior or 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/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/notifications
GovOPlaN Notifications module behavior or integration.
module/ops
GovOPlaN Ops module behavior or integration.
module/organizations
GovOPlaN Organizations module 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/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/tasks
GovOPlaN Tasks module behavior or integration.
module/templates
GovOPlaN Templates module behavior or integration.
module/tenancy
GovOPlaN Tenancy module behavior or integration.
module/views
GovOPlaN governed task views, interface projections, and workflow view integration.
module/workflow
GovOPlaN Workflow module behavior 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 Label
area/governance
codex/ready
module/campaign
module/dataflow
module/datasources
module/dms
module/postbox
priority
p1
status
ready
type
user-story
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zemion
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan#14
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?