Super Trades Workflow (Brainstorming with AI)

Notes:

Brainstorming only. We might not need to create an AI Agent workflow depending if AI is able to include our exceptions rules as we trade on market volatility and adjust our portfolio based on risk assessment and invest as needed.

If AI risks hallucinating on our exception rules, we’ll consider integrating AI on creating metrics and assessments only as opposed to a creating a trading assistant agent.

We’re seeing much higher market volatility in the ASX Funds. Therefore, the open prices and the daily swings can drastically change the Funds prices within a week, or even in just within a few days. Within our Super accounts, we can’t trade more than once on the same Fund on the same day. In addition, market prices are always changing, but not reflected within our Super account until the end of trading day, so our Super balance isn’t adjusted until the prices are reflected. In computer terms, the trading price is dynamic, but the closing price is static. We haven’t yet included within our Trading limitations/exceptions list, but regardless its still worth considering. Cybersecurity will still be on our priority list, so chances are high that we won’t be utilizing AI to be our trading assistant, but instead utilize AI to become our metrics/assessment assistant.

// Source //

Super Trades Notes

// AI Workflow // [First Diagram]

START
 └──► 1. TRADE INITIALIZATION
        ├── Assign ID from most recent BUY
        ├── Record Owner/Sector/Date/Price/Qty/Comm/Total
        └── Record commission once for split trades

 └──► 2. BUY VALIDATION
        ├── Check Tar$ limit (must not exceed)
        ├── Confirm BUY belongs to Owner group
        └── Compute LPP/TPP/CP from Owner KS
              └── TPP = LPP × 96.5%

 └──► 3. POSITION MONITORING
        ├── Monitor Lot 1 % gain
        └── Monitor TPP TG%

 └──► 4. SELL DECISION LOGIC
        ├── IF Lot 1 ≥ 3.5%
        │       └── Split SELL Lot 2
        └── IF TPP TG% ≥ 7.5%
                └── SELL Lot 1

 └──► 5. EXCEPTION OVERRIDE
        └── After Lot 1 SELL:
                └── Adjust TPP = TPP × 95%

END

// Workflow Insights 1 //

Super Trades Workflow — Insights & Recommendations (Audit‑Grade)

Concise takeaway

Your rules are internally consistent and deterministic, but there are three areas where adding structure will prevent future conflicts:

1. Lot hierarchy needs explicit dominance rules

2. TPP adjustments need a boundary condition

3. Tar$ enforcement needs a pre‑check stage

Below is the full breakdown.

1. Structural Insights

1.1 Lot Hierarchy Is Implied but Not Declared

You have rules for Lot 1 and Lot 2, but no explicit statement of priority.

• Lot 1 triggers SELL at TPP TG% ≥ 7.5%

• Lot 2 triggers SELL when Lot 1 ≥ 3.5%

This creates a dependency chain, but it’s not formally declared.

Recommendation: Add a deterministic rule stating:

• Lot Hierarchy — Lot 1 is the primary lot; Lot 2 actions cannot override Lot 1 triggers.

This prevents ambiguity when both conditions activate simultaneously.

1.2 TPP Adjustment Rule Needs a Boundary

Your override rule:

• Adjust TPP after SOLD lot 1 × 95%

This is clean, but repeated adjustments can push TPP too low, causing:

• premature SELL triggers

• misalignment with KS

• distorted TG% calculations

Recommendation: Add a minimum floor:

• TPP Floor — TPP cannot fall below LPP × 90% (or another deterministic threshold).

This keeps the system stable.

1.3 Tar$ Enforcement Needs a Pre‑Check Stage

You have:

• purchase total cannot exceed Tar$ for that Fund

• BUY trades are by Owner and Tar$ is by total

But the workflow currently checks Tar$ after recording the trade fields.

This means you could theoretically record a trade that later fails validation.

Recommendation: Add a pre‑BUY validation stage:

• Tar$ Pre‑Check — Validate Tar$ BEFORE recording Qty/Comm/Purchase Total.

This prevents invalid trades from entering the ledger.

2. Logic Insights

2.1 SELL Lot 1 and SELL Lot 2 Can Trigger Close Together

Your triggers:

• Lot 1 SELL → TPP TG% ≥ 7.5%

• Lot 2 SELL → Lot 1 ≥ 3.5%

If Lot 1 jumps from 3.5% to 7.5% quickly, both triggers activate nearly simultaneously.

Recommendation: Add a sequencing rule:

• Sell Sequencing — Lot 1 SELL always executes before Lot 2 SELL.

This prevents double‑execution conflicts.

2.2 Commission Rule Is Correct but Needs a Clarifier

You have:

• record comm once on any split trades

This is correct, but you should explicitly state:

• Commission is attached to the BUY, not the SELL.

Recommendation: Add:

• Commission Anchor — Commission is recorded only on BUY and never on SELL.

This prevents accidental duplication.

3. Missing Safeguards

3.1 No Rule for Partial Fills

If a BUY is partially filled, does it:

• create multiple IDs?

• share commission?

• count toward Tar$?

Recommendation: Add:

• Partial Fill Handling — Partial fills inherit the same ID and share commission proportionally.

3.2 No Rule for Re‑Entry After SELL

After Lot 1 SELL and TPP adjustment, do you:

• allow immediate re‑BUY?

• require cooling period?

• require new KS?

Recommendation: Add:

• Re‑Entry Logic — Define when a new BUY is allowed after a SELL event.

4. Workflow Integrity Check

Your workflow is:

• deterministic

• non‑conflicting

• logically sequenced

• exception‑aware

But adding the above safeguards will make it fully audit‑grade and prevent future rule collisions.