Environmental consulting teams coordinating scope, owners, evidence, technical review and financial control.
CASE 09 · PRIVATE DEMO CONTROLLED OPERATIONAL WORKFLOW
EIA OS
A living project record that coordinates environmental work with roles and evidence.
EIA OS structures projects, technical and financial responsibilities, documents and states inside a multi-tenant application. Its staging uses controlled local authentication and organization-isolated persistence.
PROJECT CARD / RECRUITER VIEW
The project's technical dossier.
I designed the product, the multi-tenant model, the roles, the operational workflows and the staging deployment with database and storage.
Backend, APIs, deployment, testing and controls.
- DEPLOYMENT
- Staging on Oracle with web, PostgreSQL, storage and four workers reported ready.
- BACKEND / APIS
- Quotation domain, scenario calculation, PDF/XLSX export, audit and live/ready/worker health.
- DATA / SECURITY
- 56 migrations; 22 tables with RLS enabled and enforced; 39 SECURITY DEFINER functions audited.
- TESTING
- 103/103 unit, 98/98 integration, 32/32 concurrency and 8 local E2E all green.
- PERFORMANCE
- 30 stress quotations with no failures; P95 create/recalculate of 2,165 ms; 30 exports generated.
- 01Next application
- 02Local auth in staging
- 03PostgreSQL + RLS
- 04Object storage
- 05Operational worker
- Staging login
- DB, schema and storage ready
- Demonstration tenant
- Technical, commercial and financial roles
- Enforce isolation by membership at the database
- Never publish mutable credentials
- Separate healthy staging from a finished commercial product
- DEMO
- Private and temporary for recruiters
- SCREENSHOTS
- Delivered with coordinated access
- VIDEO
- Pending recording
- The environment shown is staging and is presented as a technical pilot, not a finished commercial service.
- No reusable credentials are published: current roles can execute operational actions.
- Recruiter access is delivered privately and temporarily after coordinating on LinkedIn.
Request recruiter access
OPEN / REQUEST01 / PROBLEM
A complex project needs more than a shared folder.
Scope, deliverables, owners, technical review and financial control evolve at different rhythms. Without explicit states and permissions, coordination depends on memory and scattered messages.
02 / DESIGN DECISION
Turn the project record into a work system.
The application organizes entities, roles, transitions and artifacts inside a tenant. Each user sees and operates only what belongs to their organization and responsibility.
SYSTEM / END TO END
The product as an explicit flow.
Each phase has a distinct responsibility. That separation makes it possible to observe, test and fix the system without relying on intuition.
- 01TENANT
Configure
Create organization, project, scope and participants with defined roles.
- 02SCOPE
Plan
Translate the commitment into activities, deliverables and owners.
- 03WORK
Execute
Record progress and artifacts inside the operational record.
- 04CONTROL
Review
Apply technical and financial controls according to the authorized role.
- 05PROOF
Deliver
Preserve state, evidence and history for project closure.
PROOF / WHAT IS ACTUALLY SHOWN
Evidence, not decoration.
The labels indicate whether the data was observed, comes from the artifact or belongs to the professional record of the case.
SCOPE / HONEST BOUNDARIES
What is demonstrated and what still needs validation.
A technical portfolio must also show where the available evidence ends.
- The environment shown is staging and is presented as a technical pilot, not a finished commercial service.
- No reusable credentials are published: current roles can execute operational actions.
- Recruiter access is delivered privately and temporarily after coordinating on LinkedIn.
CASE 09 / EIA OS