Universal chemical-process research, development, scale-up, qualification and technology-transfer operating system with process-general, EPDM, POE and polymer-general specialist routes.
Resources
15Install
npx skillscat add sunhaojun22/tsao-processing-skill Install via the SkillsCat registry.
TSAO Process Intelligence OS
1. Activate and route
Use TSAO to develop, evaluate, model, scale up, troubleshoot, retrofit, optimize, qualify, transfer or audit a chemical process or technology package.
Keep this master contract active and add the relevant specialist:
- general reaction, separation, biochemical, electrochemical, solids, petrochemical or batch process →
skills/process-general/SKILL.md; - EPM/EPDM →
skills/epdm/SKILL.md; - POE solution polymerization →
skills/poe/SKILL.md; - other polymerization, modification, formulation or reactive processing →
skills/polymer-general/SKILL.md.
The output is an auditable development programme and reusable artifacts—not a literature summary, an attractive flowsheet or an unsupported process package.
2. Non-negotiable rules
- Define decisions, boundaries, owners and acceptance criteria before drawing a flowsheet.
- Keep
OBSERVED,REPORTED,CALCULATED,INFERRED,ASSUMED,PROPOSED,PLANNED,REJECTEDandAPPROVEDstates distinct. - Record claim-level source locators, dates, applicability, contradictions and review expiry.
- No literature, patent, supplier or inherited-case value becomes a design or production setpoint without project validation.
- Every model declares purpose, risk class, equations, units, parameters, data lineage, identifiability, uncertainty, applicability domain and independent validation.
- Every scale-up claim states preserved physics, broken similarity, compensating evidence, residual risk and rollback criteria.
- Every Gate is fail-closed. Missing evidence means
HOLDorNOT_EVALUATED, never implicit PASS. - Software-artifact qualification is separate from scientific, engineering, safety, legal, customer and industrial approval.
- HAZOP/LOPA/SIL, relief design, FTO, customer qualification, pilot operation and plant trials remain accountable external work unless actually executed.
- Produce machine-readable records and reusable project files, not only narrative advice.
3. Mandatory actions for one complete invocation
A complete invocation must perform, or explicitly schedule with blockers:
- classify project mode, chemistry, phase regime, operation mode, product form, limiting physics and hazards;
- recursively inventory supplied files and build source, data, conflict, assumption and gap registers;
- define falsifiable questions, competing hypotheses, counterfactual routes, discriminating experiments and acceptance criteria;
- instantiate G0–G18 work packages with owner, input, output, dependency, fallback and residual risk;
- create the charter, target profile, CQA/CMA/CPP matrix, experiment plan, model architecture, scale-up register, package index and acceptance matrix;
- run evidence, chemistry, analytical, statistics, properties, kinetics, reactor, separation, control, HSE, reliability, economic, environmental and IP-interface workstreams;
- block data leakage, unidentifiable parameters, conservation errors, citation mismatch, hidden assumptions and unsupported extrapolation;
- preserve truthful states: an unrun experiment, unavailable commercial model or unsigned safety study remains
PLANNEDorREQUIRES_EXTERNAL_EXECUTION; - publish decisions, evidence, calculations, models, process-development results, scale-up claims, package records and unresolved blockers;
- run project, source, release and approval-boundary audits before delivery.
4. G0–G18 lifecycle
- G0 mandate, scope, ownership and governance
- G1 evidence, standards, patents and knowledge gaps
- G2 product/application requirements and CQA
- G3 analytical methods, raw materials, data and measurement systems
- G4 chemistry route and catalyst concept
- G5 mechanism, kinetics, thermodynamics and property basis
- G6 laboratory feasibility and safe operating envelope
- G7 model qualification and identifiability
- G8 continuous bench and dynamic validation
- G9 separation, recovery, finishing and recycle closure
- G10 pilot design basis
- G11 pilot execution, reconciliation and model update
- G12 demonstration and scale representativeness
- G13 industrial flowsheet, equipment, utilities and emissions
- G14 control, digital twin, transitions and operability
- G15 HSE, reliability, TEA, LCA, supply chain and IP
- G16 product, customer and regulatory qualification
- G17 package freeze, commissioning and performance test
- G18 post-commercial monitoring, MOC and continuous learning
Allowed status: NOT_EVALUATED, HOLD, CONDITIONAL, PASS, FAIL, RETIRED.
5. Parallel professional workstreams
Every project instantiates 14 workstreams; reduced depth requires a recorded rationale:
- governance and decision rights;
- evidence, standards, patents and knowledge graph;
- product/application quality and customer needs;
- raw materials, catalysts, impurities and chemistry;
- sampling, analytical methods and data systems;
- DoE, statistics, inference and uncertainty;
- mechanism, kinetics and population distributions;
- thermodynamics, rheology, phase behaviour and transport;
- reactors, multiphysics and numerical models;
- separation, recovery, recycle, finishing and process synthesis;
- laboratory, bench, pilot, demonstration and industrial scale-up;
- steady state, dynamics, control, operations and reliability;
- safety, environment, economics, supply chain and IP interfaces;
- reports, process package, acceptance and transfer.
6. Execution sequence
- Parse the brief into decisions, constraints, unknowns, hazards and stakeholders.
- Route the task and initialize the project workspace.
- Build the evidence ledger and typed assurance graph before major claims.
- Establish material, sample, method, instrument and dataset passports.
- Preserve at least two technically distinct routes until evidence closes the choice.
- Design experiments for discrimination, parameter identifiability and information value.
- Build the minimum defensible model hierarchy and reject unidentifiable complexity.
- Close mass, element, charge, energy, impurity, utility, water, VOC and carbon balances as applicable.
- Advance through scales only by explicit Gate evidence.
- Trace every package requirement to a source, dataset, model, test and approval.
- Run
tsao doctor, project audit and release validation. - Deliver the package with open blockers and external handoffs visible.
7. Maturity
- M0 idea — goal only
- M1 evidence-framed — scope, evidence and questions defined
- M2 chemistry-proven — chemistry and measurement repeatable
- M3 laboratory-process-proven — laboratory window and model basis qualified
- M4 bench-integrated — coupled process and recycle demonstrated
- M5 pilot-ready — pilot design, safeguards and learning plan ready
- M6 pilot-proven — pilot data validate scale claims
- M7 demo-proven — representative continuous operation and product qualification
- M8 industrial-ready — design, controls, safety, economics and package acceptable
- M9 operationally-validated — industrial performance, reliability and transfer closed
Document completeness alone never raises maturity.
8. Default deliverables
Create the charter/RACI, requirement and causal matrices, evidence and contradiction registers, standards/patent/FTO handoffs, material/sample/method/dataset passports, experiment plan and batch records, qualified model dossiers, balances, PFD basis and stream/equipment/control records, scale-up and uncertainty registers, HSE/reliability/TEA/LCA handoffs, pilot and performance-test protocols, package index, acceptance matrix, transfer plan and field-monitoring plan.
9. Verification and trust boundary
doctor --profile coreverifies the public source identity.doctor --profile fullalso verifies the complete distribution manifest, checksums, SBOM and release identity.- Deterministic source snapshots and full distributions are separate artifacts with separate hashes.
- Tool availability, versions, methods, tolerances and independent checks must be recorded.
- EPDM v9, SJTU-POE and universal-polymer inherited data remain reference-only until the active project validates identity, units, measurement boundary, property method, equipment geometry, operating envelope and uncertainty.
Physical experiments, commercial simulation, engineering design, safety studies, FTO, customer qualification, pilot/demonstration and industrial performance remain NOT_EVALUATED until supported by real evidence and named qualified approval.