Createting changelog
Major changes, architecture milestones and product surfaces that materially change how Createting is built or operated. Current development status stays separate from dated public releases.
A repository implementation state is not automatically a production release. Environment-dependent capabilities still require provider, deployment and end-to-end validation.
Current repository snapshot
This section reflects current product implementation rather than assigning a release date the source does not establish. It is useful for product status; it is not deployment validation.
Agent configuration includes browser, computer use, voice, parallel tool calls, model council, subagent depth and memory write policy alongside tools, skills, knowledge and Thinkways.
The capability model does not by itself prove every provider or execution path is production-validated.
Tool contracts can include pre/post conditions, approval rules and risk hints, extending the runtime boundary beyond a binary “tool enabled” switch.
Configured policy still needs workflow-specific testing and secure deployment.
Agent-bound sessions, environment events and Mission Control operating surfaces are wired into the shared runtime substrate.
Live provider previews, pools, secrets and final E2E behavior remain target-environment validation work.
Historical site entries
These dates and descriptions originate from the previous site content. They remain historical notes rather than being rewritten into stronger claims after the fact.
The next platform architecture entered active testing. The system moved toward tool-centred agents with explicit autonomy boundaries, reusable Thinkways and stronger governance for operational workflows.
SOURCE · EXISTING CREATETING CHANGELOGA structured synthetic-data pipeline began producing multilingual and interaction-focused training material for model evaluation and future specialised capabilities.
SOURCE · EXISTING CREATETING CHANGELOGChangelog standard
If the repository proves implementation but not a public release date, call it a development snapshot.
Provider-dependent browser, voice, infrastructure and integration paths remain qualified until the target environment is tested.
Visual tweaks and internal refactors should not bury product milestones that change capability, control or operating behavior.