Application logs help diagnose how code ran. An action record answers a different set of questions: which customer and entity were involved, what was proposed, what authority allowed it, and what result came back.
Fibric’s reference execution path treats that record as part of the action contract. It should remain possible to connect a request to its policy decision and subsequent attempts without reconstructing the whole story from unrelated log messages.
Do not collapse distinct states
A proposed plan has not been executed. A request accepted by a service may still be pending. A transport timeout may leave the outcome uncertain. For a physical system, a command acknowledgment may require separate observation before a change can be confirmed.
Those distinctions need to survive into the product interface. “Completed” should describe the completion condition the integration can establish. If the integration cannot establish it, the record should say what is known and what requires reconciliation.
Retention, access, and recovery requirements vary by deployment. An architecture note does not establish a universal audit guarantee or a fixed retention commitment.