Workspace Status & Scope
Relevant source files
The following files were used as context for generating this wiki page:
Introduction
FLEXT is a multi-package Python workspace designed for enterprise data integration, platform tooling, and operational connectors. The workspace serves as a foundation for building integration solutions using typed, validated, and reusable primitives, primarily inheriting from a central architectural source of truth.
The "Workspace Status & Scope" governs the versioning, project boundaries, and technical standards of the flext-* ecosystem. It establishes clear boundaries between the platform core, its capabilities, and domain-specific integration packages while maintaining a strict governance chain for all agent actions and development workflows.
Sources: README.md:1-11, AGENTS.md:188-192
Workspace Versioning & Release Status
The workspace follows a strict semantic versioning (SemVer) policy to track the progress of the platform and its baseline architecture. Versions are tracked at the root level and enforced across sub-packages.
| Metric | Current Value | Description |
|---|---|---|
| Current Code Version | 0.12.0-dev | The active development version of the workspace. |
| Forward Baseline | 0.13.0 | The target architecture baseline for future releases. |
| Latest Tagged Release | v0.11.0 | The most recent stable release documented at the root. |
Sources: README.md:13-17, pyproject.toml:29
Versioning Logic
Workspace versioning is managed via utilities that parse pyproject.toml and handle semantic increments. The libs/versioning.py module provides the logic for extracting versions and identifying release tags from branch patterns.
The diagram shows how release tags are derived from branch naming conventions.
Sources: libs/versioning.py:38-51
Governed Scope & Package Hierarchy
The FLEXT workspace is organized into four primary tiers of packages. This hierarchy ensures that core platform logic is isolated from specific integration domains.
1. Platform Core
Contains the fundamental logic and infrastructure upon which all other packages are built:
flext-core,flext-infra,flext-tests,flext-quality.
2. Platform Capabilities
Provides functional services and interfaces for the platform:
flext-cli,flext-api,flext-auth,flext-web,flext-grpc,flext-observability,flext-plugin,flext-meltano.
3. Domain Packages
Targeted solutions for specific enterprise systems:
flext-ldap,flext-ldif,flext-db-oracle,flext-oracle-wms,flext-oracle-oic.
4. Integration Packages
Specific connectors for data movement and transformation:
- All
flext-tap-*,flext-target-*, andflext-dbt-*packages.
Sources: README.md:19-23
Governance & Maintenance
Workspace maintenance is driven by a "pyproject-first" philosophy where metadata is centralized in the root pyproject.toml.
Canonical Maintenance Commands
The workspace uses a unified make surface to execute maintenance tasks across different project scopes.
| Command | Purpose |
|---|---|
make build WHAT=docs | Triggers the full documentation pipeline (generate, fix, audit, build, validate). |
make check PROJECT=<name> | Runs quality gates (lint, typecheck, tests) for a specific package. |
make mod | Regenerates managed sections of pyproject.toml via flext_infra. |
Sources: scripts/maintenance/README.md:3-9, pyproject.toml:2-5, AGENTS.md:237-245
Documentation Scope
The root portal documentation is strictly limited to factual FLEXT workspace guidance. It is designed to:
- Generate API references directly from code and docstrings.
- Stop documenting non-FLEXT projects at the root level.
- Maintain architecture and migration prose in a curated format.
Sources: README.md:36-41
Infrastructure Centralization
A key part of the workspace scope is the centralization of Docker infrastructure. This prevents the proliferation of ad-hoc environment configurations in individual sub-projects.
The diagram illustrates the mandatory centralization of Docker artifacts away from project directories.
Sources: docker/README.md:22-29, docker/README.md:154-162
Prohibited Patterns
To maintain workspace integrity, certain practices are strictly forbidden:
- Creating
docker-compose.ymlorDockerfileinside project directories. - Using local
docker_fixtures.pyinstead offlext_tests.fixtures. - Bypassing the canonical
makeverbs for direct tool invocations.
Sources: docker/README.md:154-162, AGENTS.md:90-95
Conclusion
The FLEXT Workspace Status & Scope establishes a highly structured environment where versioning, package boundaries, and maintenance workflows are strictly enforced. By centralizing infrastructure and documentation while adhering to a "pyproject-first" metadata strategy, the workspace ensures consistency across its diverse set of core, capability, and integration packages.