Legal · Pine Lawyers instruments · v2022-05-26

Legal agreements, wired into the live engine.

Three instruments authored by Pine Lawyers for Flip 360 Pty Ltd. Each is a signable interactive document. Sign one, and the platform creates the partner record and seeds the commission rule against the execution ID — the legal instrument is the row that authorises the money to move.

Signing primitive · Tier 0 H003

Drawn signature pad + sha-256 anchor + IP + user-agent audit row. Same primitive as the /engage instrument. WebAuthn / hardware-bound signatures (Apple Secure Enclave · Android StrongBox) are item H302 on the Phase 1 hardening backlog — Phase 2 work.

Source Vol 4 Ch 12 · Workstream WS4 · Legal & Compliance | Vol 2 Ch 5 · Vertical 1 partner sequencing | Vol 1 Ch 8 · Programme Governance · agreement chain

The three instruments

Pine Lawyers · v2022-05-26

Introducer Agreement

Flip 360 introduces a professional to a client. The professional pays Flip 360 a percentage of every invoice raised against that client (or a fixed fee per referral). Signing creates a PARTNER contact and a commission rule.

Wires into the engine 0/0 executions countersigned

Pine Lawyers · v2022-05-26

Client Referral Agreement

A client acknowledges that Flip 360 will receive a fee from the professional they have been referred to. No fee is paid by the client. This instrument is the consumer-facing disclosure leg of the referral chain.

Acknowledgement only 0/0 executions countersigned

Pine Lawyers · v2022-05-26

Affiliate Agreement

Flip 360 (Principal) pays a third-party Affiliate a percentage of every invoice rendered to entities the Affiliate has referred. Signing creates a PARTNER contact and a commission rule that pays the Affiliate, not Flip 360.

Wires into the engine 0/0 executions countersigned

How the wiring works

1 · Counterparty opens the instrument

Flip 360 sends a partner candidate a link to /legal/introducer (or /legal/affiliate). The partner reads the document, fills the Schedule 1 fields (name, address, fee %), draws a signature, ticks the acknowledgement and submits.

2 · D1 writes the execution + signature rows

An agreement_executions row is written with the Schedule data. The signature event is hash-anchored into agreement_signatures with sha-256 over (party · name · drawn-png · timestamp · execution_ref). IP and user-agent captured for evidence.

3 · The engine receives the wiring

On Introducer or Affiliate signing, the platform automatically creates (a) a contacts row with contact_type='PARTNER', and (b) a commission_rules row carrying the execution_id as governing_agreement_execution_id. Every payout that ever runs against that rule can be traced back to the signed legal instrument.

4 · Admin sees the chain in plain view

The commission rules console gets a Governing agreement column showing the execution_ref and counterparty name for every rule. Click through to the signed instrument. Hover for the signature hash.

Provenance & document control

Source firm	Pine Lawyers · GPO Box 5218, Brisbane QLD 4001
Document version	26 May 2022 (as supplied to Flip 360)
Jurisdiction	Queensland, Australia
Principal entity	FLIP 360 PTY LTD ACN [to be inserted on incorporation]
Engine wiring authored	17 June 2026 · PMO Director (Carla Oliver, CoSai)
Backlog reference	H003 · Signature primitive v1 · evidenced today by this surface and `/engage`