OntoL-Manage Dynamic Parameters: Implementation Deep Dive

Conclusion

Dynamic parameters are the runtime JSON parameters of an instance, uniformly stored in the shared attribute of the system field action_param.

An instance is the sole carrier of dynamic parameters.

Feature ontology/behavior ontology nodes do not save action_param ; they only read the parent top-level entity via the affiliation relationship.

Therefore, the same feature ontology can be reused by multiple entities; parameter values are determined by the entity, while the feature definition itself remains stateless.

Behaviors read the dynamic parameters of their parent top-level entity through action_param (parameter table), compute via the behavior function chain, and can use the chain-tail w_action_param() to incrementally write results back to the same-level entity, achieving a "read → compute → write-back → downstream re-read" loop.

The "previous entity" in action_param() is not the path() or the previous hop on the inference chain, but the top-level entity to which the current feature/behavior ontology belongs.

Three-Layer Concept Boundaries

Dynamic Parameter

Definition: Entity-level runtime key-value parameters, JSON object.

Storage/Read Location: Stored only in entity assets, entity drafts, and entity replica nodes' ontoL_action_param; features read via affiliation relationship.

Not: Not a business field, not counted in business field quantity, not $field.

Replacement Parameter

Definition: Bare $field in DSL.

Storage/Read Location: At chain head, takes current object's field; at non-head, only takes previous function result.

Not: Not parameter storage, does not read ontoL_action_param, does not trace back across chains.

Reference Field

Definition: #field marker in documentation.

Storage/Read Location: Used only for specifications, prompts, and review materials.

Not: Does not enter parser, does not participate in data retrieval, write-back, or inference. execute.action 's params only override the replacement parameters or field values for the current execution, are not persisted, and do not write back to action_param.