SSECLOUDIS / FactoryLoading configuration

YVES SCHILLINGS · SECLOUDIS

Multi-Agentic Workflow
on AWS

Describe an application, inspect each proposal and decide whether the workflow can continue.

Loading the Factory configuration.

Your company workspace

Loading identity configuration.

WORKFLOW AND HUMAN AUTHORITY

Five worker roles, four human approval gates

  1. AnalystScope and requirements
  2. G1 ScopeYou approve the scope
  3. ArchitectDesign and interfaces
  4. G2 DesignYou approve the design
  5. Code authorInert candidate proposal
  6. TesterProposed checks
  7. ReviewerReview recommendation
  8. G3 QualityYou review the evidence
  9. G4 ReleaseYou approve this proposal

G means Gate, a human approval checkpoint. Approval applies to the exact displayed artifact. G4 records release readiness; it does not deploy an application.

01 / INPUT

What should the application do?

The request is stored with the run. The Python server derives company and project scope from the selected local identity or from the verified Cognito identity; text in the request cannot grant access.

Company and project authority come from the server. Mentioning another company in the request does not grant access to its data.

02 / PROGRESS

Your approval checkpoints

Ready
  1. 1

    G1 Scope

    Requirements and data boundaries

    Not started
  2. 2

    G2 Design

    Architecture and interface proposal

    Not started
  3. 3

    G3 Quality

    Candidate proposal and fixture checks

    Not started
  4. 4

    G4 Release

    Exact release proposal

    Not started
Start a workflow, or resume the last run saved for this company.

Controls around the Factory

Model proposal

The configured provider returns a proposal. Python validates its schema and citations before retaining it in the workflow.

Independent execution

An isolated runner is still required to execute a generated candidate and protected tests. A generated test report alone never proves that code works.

Human decision

Authorised people will inspect requirements, design, test evidence and the release target at their assigned gates.

The Factory never executes generated code or deploys a generated application. Those actions require separate, authorised delivery controls.