Process description
2to2 App Creator
Your documentation is the program. AI compiles it. The platform runs it.
App Creator is an AI-assisted editor for the analysis. It reads the procedures, policies and forms you already have, and turns them into a specification you read and approve.
That specification does not become code — it becomes an application assembled from the platform's own objects. The AI does not invent architecture; it can only use what the platform already knows how to do.
- No codebase to maintain
- The documentation is the application
- The AI assembles — it does not invent
AppSpecification/business/ process-nonconformity.md · Business process CONFIRMEDRevision 3
Business process: nonconformity handling
1. Process overview
Process code: PROC-NCR-01
Trigger: a defect or deviation found during incoming inspection, production, final inspection, a customer complaint or an audit.
Process owner: Quality Engineer
Main entities: Nonconformity, Action, Approval, Evidence, 8D case
2. Flow
Step 1 — raise. The originator enters the plant, line, source, part number, quantity and defect description. State: Submitted.
Step 2 — verification. The Quality Engineer sets the defect type and severity, and flags whether containment is required.
AI SUGGESTION FROM PROCEDURE QP-08
§4.2 has an “effectiveness verification” step after 30 days — it is missing from this description. Add it as step 7?
AppSpecification/workflows/ workflow-spec-ncr.md · Workflow specification CONFIRMEDRevision 5
Nonconformity
The life of one nonconformity, from the moment somebody on the floor raises it to the moment it is closed: verification, containment, the disposition and its approval, the customer concession when the part is under an OEM contract, the execution of the disposition and the decision whether a full 8D case is needed.
Roles
| ROLE | WHO HOLDS IT |
|---|---|
| Originator | Operators, inspectors and incoming-inspection storekeepers who raise nonconformities. |
| Quality Engineer | Verifies and classifies, carries the case; approves a disposition that is not Critical. |
| Quality Manager | Approves a Critical severity or a Use-As-Is disposition, and records the customer concession. |
| Action Owner | Carries out containment and the physical disposition. |
Fields
| FIELD | TYPE | REQ. | HOLDS |
|---|---|---|---|
| NCR Number | Text | no | NCR-YYYY-nnnnn, assigned automatically. |
| Title | Text | yes | One line saying what is wrong. |
| Source | Choice | yes | Incoming inspection, production, final inspection, complaint, audit. |
| Plant | Choice | yes | Mielec or Rzeszow. |
| Quantity | Number | yes | Pieces affected by the nonconformity. |
NCR NumberText · auto
TitleText · required
SourceChoice · 5 values
PlantChoice · 2 values
QuantityNumber
PhotosAttachments
DispositionRelation → Dispositions
NUMBERTITLEPLANTSTATE
NCR-2026-00184Hole diameter deviation, pos. 14MielecVerification
NCR-2026-00183Material certificate missingRzeszowClosed
NCR-2026-00182Coating damaged in transportMielecDisposition
NCR-2026-00181Torque out of specificationMielecClosed
A table of typed fields and relations — defined in the editor, not in database migrations.
PROCESS IN THE APPLICATIONNonconformity NCR-2026-00184 RUNNING
SubmittedHuman · Originator
TriageDigital · Triage
VerificationHuman · Engineer
DispositionHuman · Engineer
ApprovalHuman · Manager
ClosedDigital · Closure
criticalno approval neededreturned to originatorACTIVE STATESUBMITTEDHUMAN · ORIGINATORDescribe the defect, plant, part and quantity
This is a platform object — states, transitions and roles. Not code and not a drawing in a document: this is how the process looks in the editor and how it runs in the application.
Nonconformity registerPlant: allState: openMy cases
NUMBERTITLEOWNERDUE
NCR-2026-00184Hole diameter deviation, pos. 14A. Nowakin 2 days
NCR-2026-00182Coating damaged in transportM. Zajactoday
NCR-2026-00179Flange dimension out of toleranceA. Nowakin 5 days
Nonconformity registerList · visible to everyone
Quality dashboardMetrics · management
Action scheduleCalendar · action owners
Pages are views over the processes — columns, filters and access set in the editor.
The starting point
Your business already knows how the application should work.
Requirements, procedures, policies, forms, and process descriptions already contain the knowledge needed to build an application. The problem is that this knowledge is usually scattered across documents and separated from the software.
2to2 App Creator turns those sources into an executable model — without losing the business meaning behind them.
Decision logic
Policies & business rules
User experience
Forms & role descriptions
From document to application
A controlled path from business knowledge to running software.
AI accelerates the first model. Business and IT stay in control of what it means, how it works, and when it goes live.
Bring the documentation
Start with requirements, procedures, process descriptions, rules, and existing forms.
Business sourceAI structures the model
2to2 identifies the process, data, roles, permissions, pages, and decision logic.
Application specificationReview and refine
Business and IT verify the model, resolve gaps, and improve it in documentation or visual designers.
Approved living modelGenerate and run
2to2 creates the governed Process App. Publish when ready and keep improving without rebuilding from code.
Working applicationOne living model
This is not prompt-to-code.
The AI does not hand you a disconnected codebase. The structured specification remains the application model — readable by the business and executable by 2to2.
A prompt becomes a separate codebase.
- The prompt is interpreted into implementation code
- Documentation becomes stale as the code changes
- Every change creates code-level maintenance
- Governance must be added around the generated result
The specification stays the source of truth.
- Specification and application remain synchronized
- Change through documentation or visual designers
- No separate application codebase to maintain
- Workflow, permissions, and auditability live in the model
A complete application
The App Creator builds more than screens.
A Process App emerges as a connected set of business objects, not a collection of isolated UI components.
Workflow
Stages, actions, routing, approvals, exceptions, and escalation paths.
Data model
Business entities, fields, relationships, statuses, and validation constraints.
Pages & forms
Views, fields, task screens, lists, and the interfaces people use to do the work.
Roles & permissions
Who can see, start, edit, approve, delegate, and administer each part of the app.
Rules & validations
Conditions, calculations, required information, and business decision logic.
Human & AI tasks
Work assigned to people, digital workers, or both — inside one governed flow.
Every object is part of the same application model. A process change can update the user experience, permissions, and work assignments without creating disconnected logic.
Two ways to build
Write the specification. Design visually. Work on the same application.
Different teams can use the view that fits them — without creating two competing versions of the truth.
Governed by design
Generation does not mean uncontrolled publication.
AI accelerates the first model, while people remain in control. Review, test, approve, and publish through a defined lifecycle — with permissions and traceability built in.
Review before publishBusiness and IT validate the model before it becomes operational.
Built-in permissionsRoles, access, and allowed actions are part of the application model.
Traceable changeThe specification, workflow, and application remain aligned and auditable.
Questions & answers
How 2to2 App Creator works in practice.
Does 2to2 App Creator generate source code?
No. It generates and maintains an executable application model inside 2to2. There is no separate application codebase that drifts away from the specification.
Can our team continue developing the application visually?
Yes. You can improve the same model through structured documentation or 2to2 visual designers. Both approaches work on one application rather than separate artifacts.
What documentation can we start from?
Start with requirements, procedures, process descriptions, policies, role definitions, business rules, and existing forms. App Creator structures the available knowledge and helps surface gaps that need a decision.
Does AI publish the generated application automatically?
No. Generation and publication are separate. Your team can review, test, refine, and approve the model before publishing the application.
Run work. Speed up the flow.
Tell us the process you want to put on rails. We will show you the application that comes out of your own documentation.
Or write to office@datapolis.com