The questionWho owns what we build on the platform?
Skills are structured playbooks that tell an agent how to approach a class of task — how to evaluate a fibre design, triage an OSPF incident, read a vendor's counter schema. Skills built on the operator's data and operational knowledge belong to the operator, stored as inspectable text rather than opaque weights.
What we can evidence
Own the knowledge you encode, contractually and practically.
Skills built on operator data and operational knowledge belong to the operator. They are stored as inspectable, auditable text — not model weights, so they can be read, exported or transferred. Platform IP remains with Digitata Networks; domain IP remains with the operator, stated explicitly in the agreement.
Build skills three ways, including from work already done.
Digitata Networks authors an initial library during delivery; the operator's teams author their own directly in Studio; and skills can be distilled from real agent-assisted investigations — encoding what actually worked into a reusable procedure.
Turn investigations into an asset that survives staff rotation.
Studio provides full lifecycle management — creation, versioning, restoration of prior versions and refinement from real-usage feedback. A playbook written by the engineer who leaves next year remains loadable by every authorised assistant after they have gone.
What a skill actually is
A skill is a structured playbook: a set of instructions telling an agent how to approach a specific class of task. How to evaluate a fibre rollout design. How to triage an OSPF routing incident. How to interpret a particular vendor's performance counter schema, including the traps in it. Agents load skills on demand, selecting the right playbook for the task rather than carrying every procedure in every prompt.
Why inspectable text matters more than it sounds
A skill you can read is a skill you can argue with. When an agent reaches a conclusion you disagree with, the playbook it followed is a text file you can open, correct and version — not a behaviour you have to retrain around. It also means the asset is genuinely portable: an operator who ends the engagement keeps a library of documented operational procedure, not a dependency.
The compounding effect
Most operator knowledge is undocumented and resident in a handful of experienced engineers. Skills are the mechanism for converting that into something institutional. A playbook developed by the network planning team becomes loadable by any authorised assistant across the organisation, so the knowledge stops being siloed by the team that created it, and stops leaving when they do.