Patent Evolution — Refiling Considerations

Patent evolution

Refiling considerations

These are technical considerations arising from the reviewed public material, recorded for review by Murray Trento & Associates when preparing the updated provisional specification. They are not claims, and they are not statements that any material should necessarily be added.

Status

Pre-filing analysis. The expanded 2026 architecture is not filed or granted. Australian Provisional Patent Application No. 2024902103 remains the originating filing; an updated provisional specification incorporating the expanded architecture is being prepared.

12 items

HIGH — consider before refiling

9 items

MEDIUM — useful additional embodiment

7 items

WATCH — potential continuation / future development

HIGH — consider before refiling

Semantic derivative recognition independent of embedded credentials

Adobe

Observed technology: Provenance metadata is becoming an industry standard and is well covered by Adobe's public work.
Company / companies: Adobe (Content Credentials, Content Authenticity Initiative)
Relationship to existing proposed architecture: Directly engages the Digital Content Twin and rights-intelligence pillars.
Is it already adequately described?: The proposed specification contemplates a Digital Content Twin but may not sufficiently describe recognition where metadata has been stripped or was never present.
Potential additional embodiment: Describe multimodal fingerprinting and embedding comparison across video, audio, transcript and text derivatives, resolving to a single content identity record independent of any embedded credential.
Practical use case: A long-form video is re-uploaded elsewhere as a translated short clip with no credentials; the Digital Content Twin still resolves the derivative to the original work.
Reason for considering inclusion: Potential claim family: semantic content identity resolution across modality-transformed derivatives. Subject to patent counsel review.

Provenance state as an operative input to autonomous commercial decisions

Adobe

Observed technology: Provenance is publicly demonstrated as a record; its use as a live gating input to autonomous workflow is not identified in reviewed public material.
Company / companies: Adobe
Relationship to existing proposed architecture: Couples pillars 9, 10 and 13.
Is it already adequately described?: Partially — the coupling is implied rather than expressly described.
Potential additional embodiment: Describe rights state and provenance confidence as conditions on agent authority: licensing, sponsorship and distribution actions permitted, escalated or blocked based on the content twin's rights posture.
Practical use case: The Sponsorship Agent declines to place a brand against an asset whose rights posture is unresolved.
Reason for considering inclusion: Potential claim family: rights-conditioned autonomous commercial execution.

Distinguish behavioural memory from conversational/context memory

Microsoft

Observed technology: Persistent agent memory is now a documented, commoditised platform feature.
Company / companies: Microsoft (Copilot Studio, Foundry Agent Service)
Relationship to existing proposed architecture: Pillar 5 is at risk of being read as recall of prior context.
Is it already adequately described?: Insufficiently — the proposed specification should be strengthened here.
Potential additional embodiment: Describe memory records that store decision, prediction, executed action and measured outcome as a linked tuple, and a mechanism by which prediction error adjusts subsequent agent behaviour for that specific principal.
Practical use case: The Creator Agent's publishing-time recommendation shifts because previous predictions for that creator under-performed.
Reason for considering inclusion: Potential claim family: outcome-linked behavioural memory conditioning subsequent autonomous decisions.

Cross-principal agent negotiation

Microsoft

Observed technology: Delegation between co-owned agents is publicly documented; negotiation between agents with opposed commercial interests is not identified in reviewed public material.
Company / companies: Microsoft (connected agents), Google (A2A), Salesforce (Agentforce)
Relationship to existing proposed architecture: Pillars 3 and 13.
Is it already adequately described?: Named in the proposed architecture but requires deeper technical embodiment.
Potential additional embodiment: Describe capability advertisement, offer/counter-offer exchange, constraint and entitlement checking, human approval thresholds, and the recording of negotiation outcomes to both parties' twins.
Practical use case: Creator Agent and Sponsorship Agent converge on preliminary sponsorship terms for human ratification.
Reason for considering inclusion: Potential claim family: autonomous inter-principal commercial negotiation with approval gating.

Creator-owned, portable behavioural twin

Meta

Observed technology: Platform-resident creator assistants that learn goals over time are now publicly demonstrated.
Company / companies: Meta (Creator Assistant)
Relationship to existing proposed architecture: Pillars 2, 4 and 5 — the core of the creator-side position.
Is it already adequately described?: The proposed specification describes Creator Digital Twins but should more expressly address ownership, portability and cross-platform derivation.
Potential additional embodiment: Describe a twin constructed from behavioural signals across multiple independent platforms, held under the creator's control, exportable and usable to condition agents acting on any connected platform.
Practical use case: A creator's twin, built from four platforms, informs strategy on a fifth platform newly connected.
Reason for considering inclusion: Potential claim family: principal-owned cross-platform behavioural model conditioning autonomous action on unaffiliated platforms.

Viewer-principal suppression and pre-emptive retrieval

Meta

Observed technology: Platform-side ranking optimises for engagement; viewer-side suppression on the viewer's behalf is not identified in reviewed public material.
Company / companies: Meta (recommendation systems, by contrast)
Relationship to existing proposed architecture: Pillars 3, 11 and 14.
Is it already adequately described?: Described but under-specified.
Potential additional embodiment: Describe a viewer agent computing predicted future relevance and deferring, summarising, batching or suppressing notifications and content across multiple platforms, then updating the Viewer Twin from whether deferred items were later sought.
Practical use case: A viewer receives one weekly consolidated brief instead of 300 platform notifications.
Reason for considering inclusion: Potential claim family: predicted-future-relevance information suppression with outcome feedback.

Negotiation semantics layered over open agent protocols

Google

Observed technology: Open agent interoperability is now standardised and widely adopted.
Company / companies: Google (A2A), Salesforce, Microsoft
Relationship to existing proposed architecture: Pillars 3 and 13.
Is it already adequately described?: The proposed specification describes agent negotiation but not protocol-independent semantics.
Potential additional embodiment: Describe negotiation state, offer representation, entitlement verification and approval thresholds as a layer capable of operating over any agent-interoperability transport.
Practical use case: A creator's agent negotiates with an external brand's agent operated by a third party.
Reason for considering inclusion: Potential claim family: transport-independent inter-agent commercial negotiation state machine.

Cross-platform semantic derivative resolution

Google

Observed technology: Intra-platform reference matching is operationally mature (Content ID).
Company / companies: Google
Relationship to existing proposed architecture: Pillars 9 and 10.
Is it already adequately described?: Requires strengthening to avoid being read onto fingerprint matching.
Potential additional embodiment: Describe resolution of a derivative across a modality change (video → transcript → article → translated summary) and across unaffiliated platforms, with a confidence-scored lineage record.
Practical use case: A summarised article derived from a creator's video on an unrelated site is linked to the original work.
Reason for considering inclusion: Potential claim family: cross-platform cross-modality derivative lineage resolution.

Explicitly claim the twin as distinct from the memory store

Amazon Web Services

Observed technology: Managed agent memory is now a standard cloud primitive.
Company / companies: AWS (AgentCore Memory), Google (Memory Bank)
Relationship to existing proposed architecture: Pillars 4 and 5.
Is it already adequately described?: The distinction is implicit and should be made explicit.
Potential additional embodiment: Describe the Digital Twin as a derived, queryable predictive model maintained from the memory store, capable of answering forward-looking questions the raw memory cannot.
Practical use case: The twin answers 'what will this audience do next quarter', which a memory store cannot.
Reason for considering inclusion: Potential claim family: predictive behavioural model derived from and continuously reconciled with an interaction memory store.

Distinguish behavioural twin from unified customer profile

Salesforce

Observed technology: Unified profile platforms with harmonised behavioural history are mature and widely deployed.
Company / companies: Salesforce (Data Cloud), Adobe (Experience Platform)
Relationship to existing proposed architecture: Pillar 4 — the most exposed pillar in the mapping.
Is it already adequately described?: Insufficiently.
Potential additional embodiment: Describe the twin as a simulation-capable model able to evaluate hypothetical actions before execution and to be corrected by realised outcomes, expressly beyond a stored profile or segment membership.
Practical use case: The Creator Twin evaluates three candidate publishing strategies before one is executed.
Reason for considering inclusion: Potential claim family: counterfactual evaluation against a behavioural twin prior to autonomous execution.

Creator-side commercial agent representation

Salesforce

Observed technology: Enterprise-side commercial agents are publicly demonstrated; agents representing the individual counterparty are not identified in reviewed public material.
Company / companies: Salesforce (Agentforce, Marketing Cloud)
Relationship to existing proposed architecture: Pillars 2, 3 and 13.
Is it already adequately described?: Named; requires deeper embodiment.
Potential additional embodiment: Describe a Creator Agent evaluating inbound brand offers against twin-derived audience valuation and declining, countering or escalating them.
Practical use case: A creator's agent counters a sponsorship offer using predicted audience value.
Reason for considering inclusion: Potential claim family: principal-side autonomous evaluation of inbound commercial offers.

Express claim language distinguishing behavioural from physical twins

NVIDIA

Observed technology: Digital Twin terminology is dominated in public technical literature by physical and industrial simulation.
Company / companies: NVIDIA (Omniverse)
Relationship to existing proposed architecture: Pillar 4 across the whole specification.
Is it already adequately described?: Not expressly.
Potential additional embodiment: Define the twin in the specification by its inputs (behavioural, engagement, commercial and content events) and its outputs (predicted behaviour and recommended action for the modelled principal), avoiding reliance on the term alone.
Practical use case: Clear separation from industrial twin prior art during examination.
Reason for considering inclusion: Drafting consideration rather than a new claim family. Subject to patent counsel review.

MEDIUM — useful additional embodiment

Prediction-conditioned content transformation

Adobe

Observed technology: Programmatic variant generation is publicly demonstrated at scale by Firefly Services.
Company / companies: Adobe
Relationship to existing proposed architecture: Pillars 7 and 8.
Is it already adequately described?: The proposed specification describes transformation but may under-describe the selection mechanism.
Potential additional embodiment: Describe selection of which derivative formats to produce, for which platform and at which time, from Digital Twin state and predicted engagement, with realised outcomes updating the prediction model.
Practical use case: The Creator Agent produces only the three derivative formats predicted to exceed a retention threshold for that creator's audience.
Reason for considering inclusion: Potential claim family: outcome-predictive derivative selection.

Autonomous trigger semantics for behavioural events

Microsoft

Observed technology: Autonomous event triggers for agents are documented.
Company / companies: Microsoft
Relationship to existing proposed architecture: Pillars 1, 14 and 18.
Is it already adequately described?: Partially.
Potential additional embodiment: Describe triggers derived from predicted behavioural change (predicted audience migration, predicted churn of a subscriber cohort) rather than from discrete system events.
Practical use case: The Creator Agent acts on predicted audience migration before it is observable in platform analytics.
Reason for considering inclusion: Potential claim family: prediction-derived autonomous workflow triggers.

Cross-platform audience overlap and migration

Meta

Observed technology: Single-platform audience analytics are mature and publicly documented.
Company / companies: Meta
Relationship to existing proposed architecture: Pillar 12.
Is it already adequately described?: Described at a high level.
Potential additional embodiment: Describe overlap inference, migration detection and loyalty scoring computed across independent platforms without requiring shared identifiers, including privacy-preserving techniques.
Practical use case: Detection that a cohort is migrating from one platform to another before revenue declines.
Reason for considering inclusion: Potential claim family: privacy-preserving cross-platform audience migration inference.

Outcome-derived memory

Google

Observed technology: Conversation-derived long-term memory is documented and productised.
Company / companies: Google (Memory Bank), AWS (AgentCore Memory)
Relationship to existing proposed architecture: Pillar 5.
Is it already adequately described?: Partially.
Potential additional embodiment: Describe memory items generated from executed external actions and their measured results, not from dialogue.
Practical use case: The agent remembers that Tuesday releases underperform for this creator's audience.
Reason for considering inclusion: Potential claim family: action-outcome memory synthesis.

Federated behavioural learning across independent operators

Amazon Web Services

Observed technology: Privacy and isolation are strong, but cross-operator federated behavioural learning is not identified in reviewed public material.
Company / companies: AWS (by contrast)
Relationship to existing proposed architecture: Pillar 16.
Is it already adequately described?: Named but under-specified.
Potential additional embodiment: Describe secure aggregation of behavioural gradients across platform boundaries so ecosystem models improve without centralising raw viewer data.
Practical use case: Cross-platform audience models improve without any platform disclosing viewer-level data.
Reason for considering inclusion: Potential claim family: federated cross-platform behavioural model improvement.

Behaviour-generated workflows

Amazon Web Services

Observed technology: Durable workflow orchestration assumes a pre-defined workflow graph.
Company / companies: AWS (Step Functions)
Relationship to existing proposed architecture: Pillars 1, 7 and 18.
Is it already adequately described?: Partially.
Potential additional embodiment: Describe generation of the workflow definition itself from twin state and prediction, then execution and measurement of that generated workflow.
Practical use case: The orchestrator composes a new distribution workflow for an unusual audience condition.
Reason for considering inclusion: Potential claim family: predictive generation of executable orchestration workflows.

Entitlement and rights state in commercial orchestration

Salesforce

Observed technology: Commercial orchestration is mature but rights-aware gating is not identified in reviewed public material.
Company / companies: Salesforce
Relationship to existing proposed architecture: Pillars 10 and 13.
Is it already adequately described?: Partially.
Potential additional embodiment: Describe entitlement objects binding content twins, agreements and permitted commercial actions, enforced at execution time.
Practical use case: A licensing action is blocked because the underlying derivative's rights posture is unresolved.
Reason for considering inclusion: Potential claim family: entitlement-bound commercial action execution.

Simulation before execution

NVIDIA

Observed technology: Simulating a change against a twin before applying it in the real system is standard practice in industrial twins.
Company / companies: NVIDIA
Relationship to existing proposed architecture: Pillars 4, 7 and 18.
Is it already adequately described?: Not identified in the present proposed specification.
Potential additional embodiment: Describe simulating candidate creator strategies, notification policies or commercial terms against the behavioural twin and selecting by simulated outcome before external execution.
Practical use case: A pricing change is simulated against the audience twin before being applied.
Reason for considering inclusion: Potential claim family: pre-execution simulation of candidate actions against a behavioural twin.

Twin fidelity and drift management

NVIDIA

Observed technology: Industrial twin practice includes explicit synchronisation and fidelity measurement.
Company / companies: NVIDIA
Relationship to existing proposed architecture: Pillars 4, 5 and 18.
Is it already adequately described?: Not identified.
Potential additional embodiment: Describe measuring divergence between twin predictions and observed behaviour, and triggering re-modelling or reduced agent autonomy when drift exceeds a threshold.
Practical use case: Agent autonomy is automatically reduced when the twin's predictions degrade.
Reason for considering inclusion: Potential claim family: twin-fidelity-conditioned autonomy control.

WATCH — potential continuation / future development

Brand intelligence as a constraint on creator-side autonomous action

Adobe

Observed technology: Adobe publicly describes brand intelligence informing agentic content creation.
Company / companies: Adobe
Relationship to existing proposed architecture: Pillars 2 and 13 (Brand AI Agent).
Is it already adequately described?: The Brand AI Agent is named but lightly described.
Potential additional embodiment: Describe negotiated constraint exchange between a Brand Agent and a Creator Agent, where brand-side constraints are enforced on autonomously produced creator derivatives.
Practical use case: Sponsored creator derivatives are auto-validated against brand constraints before publication.
Reason for considering inclusion: Potential future continuation: cross-principal constraint negotiation.

Governance and approval architecture

Microsoft

Observed technology: Enterprise governance of autonomous agents is comparatively mature.
Company / companies: Microsoft
Relationship to existing proposed architecture: Pillar 1 and 17.
Is it already adequately described?: Lightly.
Potential additional embodiment: Describe explainability records as the audit substrate for autonomous commercial action, retained per decision.
Practical use case: A creator reviews why an agent declined a sponsorship.
Reason for considering inclusion: Potential future continuation: explainability-linked autonomous action audit.

Automated multilingual derivative distribution

Meta

Observed technology: AI translation and dubbing features are being publicly deployed across creator platforms.
Company / companies: Meta, Google (YouTube)
Relationship to existing proposed architecture: Pillars 8 and 9.
Is it already adequately described?: Described as a transformation output.
Potential additional embodiment: Describe translated derivatives remaining bound to the Digital Content Twin for rights and revenue attribution.
Practical use case: Revenue from a dubbed derivative is attributed to the original work's rights record.
Reason for considering inclusion: Potential future continuation: derivative-bound rights and revenue attribution.

Multimodal retrieval conditioned on behavioural state

Google

Observed technology: Multimodal reasoning is commoditised at model level.
Company / companies: Google (Gemini)
Relationship to existing proposed architecture: Pillar 11.
Is it already adequately described?: Described generically.
Potential additional embodiment: Describe retrieval ranking conditioned jointly on semantic similarity and Viewer Twin state including previously suppressed items.
Practical use case: Two viewers issue the same query and receive materially different result sets.
Reason for considering inclusion: Potential future continuation: twin-conditioned multimodal retrieval.

Edge and hybrid execution of viewer agents

Amazon Web Services

Observed technology: Hybrid and edge deployment is well supported at infrastructure level.
Company / companies: AWS
Relationship to existing proposed architecture: Pillar 16.
Is it already adequately described?: Mentioned.
Potential additional embodiment: Describe viewer-agent inference executing on device with only aggregated updates returned.
Practical use case: Viewer behavioural state never leaves the device.
Reason for considering inclusion: Potential future continuation: on-device viewer twin with aggregated update return.

Agent observability as an explainability substrate

Salesforce

Observed technology: Agent observability tooling is a public focus of recent Agentforce releases.
Company / companies: Salesforce
Relationship to existing proposed architecture: Pillar 17.
Is it already adequately described?: Described generally.
Potential additional embodiment: Describe per-decision explanation records retained and presented to the principal on request.
Practical use case: A creator asks why a post was scheduled for a particular time and receives the contributing factors.
Reason for considering inclusion: Potential future continuation: principal-facing decision explanation records.

Community twins as multi-agent simulated populations

NVIDIA

Observed technology: Large-scale multi-agent simulation is publicly demonstrated in industrial contexts.
Company / companies: NVIDIA
Relationship to existing proposed architecture: Pillar 4 (Community Digital Twin).
Is it already adequately described?: Named only.
Potential additional embodiment: Describe a community twin as a population of viewer twin instances whose aggregate simulated response informs creator strategy.
Practical use case: A creator tests a format change against a simulated audience population.
Reason for considering inclusion: Potential future continuation: population-level behavioural simulation for content strategy.