AI Profile Solver
The AI Profile Solver is optional. CoCo Asset Flow remains fully usable with Profile Editor or handwritten JSON.
The package does not contain:
- an LLM;
- an API key;
- a network client;
- an autonomous asset processor;
- an Agent Apply entry point.
Authority model
Section titled “Authority model”An external Agent may:
- read one fresh Source-bound Inventory;
- read Cleanup Profile v1 Schema;
- read repository conventions selected by the user;
- write one disclosed
*.cleanup.json; - write its adjacent
*.cleanup.rationale.md; - request Schema Validation and read-only Preview.
It may not:
- edit
.meta; - move, rename, or delete Unity assets;
- rewrite source images;
- generate a C# asset processor;
- call Apply.
If Profile v1 cannot express a requirement, the Agent reports it as Unsupported and stops.
Install the optional Sample
Section titled “Install the optional Sample”In Package Manager, import AI Profile Solver.
Importing the package or Sample never writes the host project’s .agents folder and never overwrites Agent configuration.
The Sample includes:
- Agent-neutral workflow documentation;
- Profile contract and capability matrix;
- Source-bound Inventory locator;
- Inventory/Profile/rationale examples;
- an optional Codex Skill adapter.
Installing the Skill for an Agent is a separate, explicit user action.
Solve a Profile
Section titled “Solve a Profile”1. Select the Source
Section titled “1. Select the Source”In Cleanup Runner, select the exact Source folder.
2. Export fresh evidence
Section titled “2. Export fresh evidence”Choose Scan / Export for AI. Then use Copy Solver Request, which includes:
- Source path;
- Inventory path;
- generated time and hash;
- Schema path;
- suggested Profile and rationale paths;
- the no-Apply authority boundary.
3. Identify authoritative conventions
Section titled “3. Identify authoritative conventions”Tell the Agent which repository documents define:
- naming;
- destinations;
- Texture semantics;
- Prefab cleanup;
- FBX animation behavior;
- allowed deletion.
Do not allow the Agent to treat third-party files inside Source as repository authority.
If no convention exists, state that explicitly. The optional Common 3D fallback is only a non-authoritative reference and must be ignored when the user supplies a convention.
4. Review the proposed files
Section titled “4. Review the proposed files”The Agent should disclose and modify only:
Assets/CoCoAssetFlow/Profiles/<Source-specific-name>.cleanup.jsonAssets/CoCoAssetFlow/Profiles/<Source-specific-name>.cleanup.rationale.mdThe rationale should record the Inventory identity, chosen conventions, rule basis, uncertainty, Unsupported requirements, and latest Preview result.
5. Validate and Preview in Unity
Section titled “5. Validate and Preview in Unity”Load the saved Profile in Cleanup Runner and choose Validate + Preview.
Iterate until:
- Schema and semantic validation pass;
- unmatched assets are resolved;
- collisions are resolved;
- Blocker count is zero;
- Unsupported requirements are either accepted as out of scope or handled outside this run.
6. Apply separately
Section titled “6. Apply separately”The Agent does not confirm Apply. The user reviews the final Unity Dry Run and separately confirms its exact Plan ID.