From your Stack to factoring submission

• PersonDecides. Every approval, tap and spoken word is a person’s.
• Intelligence · draftsReads and drafts, citing its sources. It never sends or approves.
• Automation · acts within authorityCarries out the work an organization authorized, and nothing beyond it.
• System or partnerA participant’s own software, or a partner it connected, in any of the Ecosystem’s categories: verify and assure, hire and keep drivers, run the load, equip and fuel, get paid, comply. Each confirms what it does and returns its own reference; its badge names its category, or says it is the participant’s own system. A public record, such as FMCSA, is shown as a public record, not a partner.

1. 1 Stack: Connect the Stack, once

   The broker connects its TMS and an assurance partner. The carrier connects its ELD, its own factoring company, its fuel card and its hiring partner. Each connection returns a reference.

   6 by people · 1 by TruckerTech · 2 of their own systems · 4 partners · 3 organizations

   1. PersonMorgan K.Example Broker

      Morgan K. opens the empty TMS port. The Ecosystem Exchange slides out with TMS partners, and Morgan drags Example TMS Co. onto the port.

      Why it’s safe A paid place is labelled: Sponsored at the top of this category, Featured in the one spot above every category. Payment never changes how the other partners rank, or any partner’s standing.

   2. Their system · TMSExample TMS Co.for Example Broker

      Connected · reference returned. Morgan signed in at Example TMS Co., which confirms and returns AC-2207.

      Why it’s safe Your TMS stays your system of record. TruckerTech never sees the password, and writes into the TMS only through this connection.

      From

      Example TMS Co. · Example Broker’s TMS

      To

      Example Broker’s Stack · TruckerTech

      Reference

      AC-2207

   3. Automation · acts within authorityAutomationfor Example Broker

      Runs the first health check on Example TMS Co.: Operational.

   4. PersonMorgan K.Example Broker

      Morgan also connects an assurance partner: Example Coverage Co. keeps each carrier’s insurance certificate on file and current.

      Why it’s safe Example Broker chose it and holds the connection. A partner’s standing is shown as it is; it is never something a partner can buy.

   5. Partner · Insurance and certificatesExample Coverage Co.for Example Broker

      Confirms the connection and returns its reference.

      From

      Example Coverage Co. · Example Broker’s insurance and COI partner

      To

      Example Broker’s Stack · TruckerTech

      Reference

      AC-4471

   6. PersonSam T.Example Carrier

      The camera moves to Example Carrier. Sam T. presses Connect on the ELD port and signs in at Example Telematics Co.

      Why it’s safe Connect is the button way to do what the drag does. Positions are shared only on loads Example Carrier takes part in.

   7. Their system · ELD and telematicsExample Telematics Co.for Example Carrier

      Confirms the connection and returns its reference.

      From

      Example Telematics Co. · Example Carrier’s ELD

      To

      Example Carrier’s Stack · TruckerTech

      Reference

      AC-5180

   8. PersonSam T.Example Carrier

      Sam connects Example Carrier’s own factoring company, Example Factoring Co.

      Why it’s safe It is the carrier’s connection, held by the organization. Credit approvals and funding status come back to Example Carrier only.

   9. Partner · Factoring and credit approvalExample Factoring Co.for Example Carrier

      Confirms the connection and returns its reference.

      From

      Example Factoring Co. · Example Carrier’s factoring connection

      To

      Example Carrier’s Stack · TruckerTech

      Reference

      AC-3316

   10. PersonSam T.Example Carrier

       Connects its fuel card, Example Fuel Network Co..

   11. Partner · Fuel cards and discountsExample Fuel Network Co.for Example Carrier

       Confirms the connection and returns its reference.

       From

       Example Fuel Network Co. · Example Carrier’s fuel card partner

       To

       Example Carrier’s Stack · TruckerTech

       Reference

       AC-6620

   12. PersonSam T.Example Carrier

       Then the partners that run its drivers’ day: fuel through Example Fuel Network Co., hiring and onboarding through Example Driver Hiring Co.

       Why it’s safe Each is a partner Example Carrier chose. TruckerTech never handles their sign-ins, and each returns its own reference.

   13. Partner · Recruiting and ATSExample Driver Hiring Co.for Example Carrier

       Confirms the connection and returns its reference.

       From

       Example Driver Hiring Co. · Example Carrier’s hiring partner (ATS)

       To

       Example Carrier’s Stack · TruckerTech

       Reference

       AC-7395

2. 2 Tender: A tender becomes Core 48213

   A shipper’s tender arrives by email. Intelligence drafts the load, the broker approves, and the Core is written into the broker’s TMS.

   1 by people · 5 by TruckerTech · 2 of their own systems · 0 partners · 2 organizations

   1. Their system · Email and messagingExample Mail Co.for Example Broker

      A tender from Example Shipper Co. arrives by email, the way it always has.

      Why it’s safe TruckerTech reads it through Example Broker’s own email connection. Nothing is sent or created yet.

      From

      Example Mail Co. · Example Broker’s email

      To

      Core 48213 · TruckerTech

      Reference

      MSG-80412

   2. Intelligence · draftsIntelligencefor Example Broker

      Intelligence reads the tender into a draft. Every field shows where it came from, and the one it inferred is marked Inferred.

      Why it’s safe Intelligence reads and drafts. It cannot create a Core or reply to anyone: Morgan approves.

   3. Intelligence · draftsIntelligencefor Example Broker

      Checks Example Broker’s open loads for a duplicate: none.

   4. PersonMorgan K.Example Broker

      Morgan K. checks the one inferred field and approves.

      Why it’s safe Approving is Morgan’s act, recorded with Morgan’s name and authority.

   5. Automation · acts within authorityAutomationfor Example Broker

      Creates Core 48213, carrying the shipper’s own number.

      From

      Example Mail Co. · Example Broker’s email

      To

      Core 48213 · TruckerTech

      Reference

      SO-118204

   6. Automation · acts within authorityAutomationfor Example Broker

      Automation creates Core 48213 and writes it into Example Broker’s TMS. Example TMS Co. confirms and returns BRK-77310.

      Why it’s safe It acts under the operations workflow Example Broker turned on, after Morgan’s approval. The write counts only once the TMS confirms it.

      From

      Core 48213 · TruckerTech

      To

      Example TMS Co. · Example Broker’s TMS

      Reference

      BRK-77310

   7. Automation · acts within authorityAutomationfor Example Broker

      Example Shipper Co. sees Core 48213 under its own number, SO-118204, with the broker’s acceptance.

      Why it’s safe Each seat sees only its part. The shipper never sees Example Broker’s margin or what the carrier is paid.

      From

      Core 48213 · TruckerTech

      To

      Example Shipper Co.’s seat · TruckerTech

      Reference

      SO-118204

3. 3 Carrier: Verified, drafted, accepted

   Protect checks the carrier with FMCSA and assurance partners. The carrier’s own factor approves the broker’s credit. Intelligence drafts the rate confirmation, the broker approves, and the carrier accepts.

   2 by people · 5 by TruckerTech · 1 of their own systems · 3 partners · 1 public record · 3 organizations

   1. Automation · acts within authorityAutomationfor Example Broker

      TruckerTech Protect checks Example Carrier before any load moves: the FMCSA record, then Example Broker’s assurance partners.

      Why it’s safe Every Core Example Broker creates is protected the same way. A check against the record and the partners’ data, never a score anyone can buy.

   2. Public record · Business verificationFMCSAfor Example Broker

      Operating authority active for MC 100412.

      From

      FMCSA · public record

      To

      Core 48213 · TruckerTech

      Reference

      MC 100412

   3. Partner · Insurance and certificatesExample Coverage Co.for Example Broker

      Assurance partner: Example Coverage Co. confirms Example Carrier’s insurance certificate is on file and current.

      Why it’s safe It comes through Example Broker’s own connection, with its source and date. Protect shows the partner’s answer; it does not invent one.

      From

      Example Coverage Co. · Example Broker’s insurance and COI partner

      To

      Core 48213 · TruckerTech

      Reference

      COI-30918

   4. Partner · Safety score and CSA monitoringExample Safety Ratings Co.for Example Broker

      Safety score within Example Broker’s threshold.

      From

      Example Safety Ratings Co. · Example Broker’s safety score partner

      To

      Core 48213 · TruckerTech

      Reference

      SAF-22104

   5. Intelligence · draftsIntelligencefor Example Broker

      Intelligence drafts the rate confirmation from the Core: lane, windows, equipment and terms.

      Why it’s safe Drafted by Intelligence, for review. It never sends: approving sends it, as Morgan.

   6. PersonMorgan K.Example Broker

      Approves the rate confirmation; it goes to Sam T. as Morgan.

      From

      Example Broker’s seat · TruckerTech

      To

      Example Carrier’s seat · TruckerTech

      Reference

      RC-48213

   7. Partner · Factoring and credit approvalExample Factoring Co.for Example Carrier

      On Example Carrier’s canvas, its own factor reports that Example Broker is credit-approved.

      Why it’s safe The decision comes from Example Carrier’s factor, through its own connection. TruckerTech computes no credit score, and Example Broker never sees this.

      From

      Example Factoring Co. · Example Carrier’s factoring connection

      To

      Example Carrier’s seat · TruckerTech

      Reference

      CR-55127

   8. PersonSam T.Example Carrier

      Sam T. accepts the rate confirmation for Example Carrier.

      Why it’s safe Accepting is Sam’s act, recorded with Sam’s name and authority. Live Acceptance comes later, from the driver Example Carrier assigns.

   9. Automation · acts within authorityAutomationfor Example Carrier

      Records Sam T.’s acceptance of RC-48213 on Core 48213, for both parties.

   10. Automation · acts within authorityAutomationfor Example Carrier

       Automation writes the load into Example Carrier’s TMS, Example Dispatch Suite, which returns LD-5521.

       Why it’s safe Through Example Carrier’s own connection and authority. That record holds only what the carrier’s seat may see.

       From

       Core 48213 · TruckerTech

       To

       Example Dispatch Suite · Example Carrier’s TMS

       Reference

       LD-5521

   11. Automation · acts within authorityAutomationfor Example Carrier

       Files the signed rate confirmation with Example Dispatch Suite.

       From

       Core 48213 · TruckerTech

       To

       Example Dispatch Suite · Example Carrier’s TMS

       Reference

       LD-5521 · RC-48213

4. 4 Dispatch: A driver, a phone, an appointment

   The carrier picks a driver it hired through the Career Network, with the qualification file on hand from its partners. The load appears on the driver’s phone, the driver proves presence with Live Acceptance, and Automation asks the receiver for a delivery appointment.

   2 by people · 7 by TruckerTech · 3 of their own systems · 3 partners · 3 organizations

   1. Intelligence · draftsIntelligencefor Example Carrier

      Intelligence lists who can take the load, with hours of service read from the ELD.

      Why it’s safe It suggests; it does not assign. Every fact shows its source and how old it is.

      From

      Example Telematics Co. · Example Carrier’s ELD

      To

      Core 48213 · TruckerTech

      Reference

      HOS · tractor 214

   2. Partner · Recruiting and ATSExample Driver Hiring Co.for Example Carrier

      Riley came to Example Carrier through the Career Network. Its hiring partner, Example Driver Hiring Co., holds the onboarding and qualification file.

      Why it’s safe The file stays with Example Carrier and its partner. ID Secure secures Riley’s own TTID, and no other organization is shown it.

      From

      Example Driver Hiring Co. · Example Carrier’s hiring partner (ATS)

      To

      Example Carrier’s seat · TruckerTech

      Reference

      DQF-2211

   3. Partner · Driver screening and checksExample Driver Records Co.for Example Carrier

      Reports Riley M.’s MVR and Clearinghouse query on file.

      From

      Example Driver Records Co. · Example Carrier’s driver records partner

      To

      Example Carrier’s seat · TruckerTech

      Reference

      MVR-8840

   4. Partner · Maintenance and inspectionExample Fleet Service Co.for Example Carrier

      Reports tractor 214’s inspection current, with no open defects.

      From

      Example Fleet Service Co. · Example Carrier’s maintenance and inspection partner

      To

      Example Carrier’s seat · TruckerTech

      Reference

      INS-3307

   5. PersonSam T.Example Carrier

      Sam assigns Riley M. and tractor 214.

      Why it’s safe Assigning is Sam’s decision, recorded with Sam’s name.

   6. Automation · acts within authorityAutomationfor Example Carrier

      Writes the assignment into Example Dispatch Suite.

      From

      Core 48213 · TruckerTech

      To

      Example Dispatch Suite · Example Carrier’s TMS

      Reference

      LD-5521 · DSP-3307

   7. Automation · acts within authorityAutomationfor Example Carrier

      Riley’s phone shows the load: the stops, the windows and one large button.

      Why it’s safe Riley sees stops and windows only, never the rate or the broker’s terms.

      From

      Core 48213 · TruckerTech

      To

      Riley M.’s phone · TruckerTech

      Reference

      LD-5521

   8. PersonRiley M.Example Carrier

      Riley holds a current ID Secure, so Live Acceptance is a Secure Presence step-up on the phone: a passkey on this device and its biometric, bound to this assignment.

      Why it’s safe Example Broker and Example Shipper Co. see only that Live Acceptance was completed for this assignment. Riley’s ID Secure and biometrics are never shown to them.

   9. Automation · acts within authorityAutomationfor Example Carrier

      Records “Live Acceptance completed” for this assignment on Core 48213.

      From

      Riley M.’s phone · TruckerTech

      To

      Core 48213 · TruckerTech

      Reference

      LA-48213-1

   10. Automation · acts within authorityAutomationfor Example Broker

       Automation asks Example Facility’s dock scheduling for a delivery appointment.

       Why it’s safe It asks through Example Facility’s own scheduling connection and may request, never confirm: only Example Facility confirms a slot at its own dock.

       From

       Core 48213 · TruckerTech

       To

       Example Scheduling Co. · Example Facility’s dock scheduling

       Reference

       REQ-7716

   11. Their system · Scheduling and appointmentsExample Scheduling Co.for Example Facility

       Example Facility’s system confirms Fri 6:00–8:00 AM and returns APPT-0931.

       Why it’s safe The appointment lives in the facility’s own system. The Core holds its reference.

       From

       Example Scheduling Co. · Example Facility’s dock scheduling

       To

       Core 48213 · TruckerTech

       Reference

       APPT-0931

   12. Automation · acts within authorityAutomationfor Example Carrier

       Puts the appointment on Riley M.’s phone.

       From

       Core 48213 · TruckerTech

       To

       Riley M.’s phone · TruckerTech

       Reference

       APPT-0931

   13. Automation · acts within authorityAutomationfor Example Carrier

       Writes the appointment into Example Dispatch Suite.

       From

       Core 48213 · TruckerTech

       To

       Example Dispatch Suite · Example Carrier’s TMS

       Reference

       LD-5521 · APPT-0931

5. 5 In transit: Late risk, caught and fixed

   The driver fuels on the carrier’s fuel card. The carrier’s ELD reports the ETA; Intelligence sees the delivery will be late and proposes a fix; the broker approves; Automation moves the appointment, and the carrier’s own Automation updates its side.

   1 by people · 7 by TruckerTech · 3 of their own systems · 1 partner · 4 organizations

   1. Partner · Fuel cards and discountsExample Fuel Network Co.for Example Carrier

      Riley fuels tractor 214 on Example Carrier’s fuel card. Fuel partner: Example Fuel Network Co. reports the purchase at the network price.

      Why it’s safe It lands on Example Carrier’s side of Core 48213 only. Example Broker never sees the carrier’s fuel.

      From

      Example Fuel Network Co. · Example Carrier’s fuel card partner

      To

      Example Carrier’s seat · TruckerTech

      Reference

      FUEL-55813

   2. Automation · acts within authorityAutomationfor Example Carrier

      Adds the fuel purchase to the load’s costs in Example Dispatch Suite.

      From

      Example Carrier’s seat · TruckerTech

      To

      Example Dispatch Suite · Example Carrier’s TMS

      Reference

      LD-5521 · FUEL-55813

   3. Their system · ELD and telematicsExample Telematics Co.for Example Carrier

      Example Carrier’s ELD reports the ETA onto the Core through its connector: now 9:10 AM.

      Why it’s safe This load only, with the source and age. Positions are used for the ETA and never kept, and Example Broker never sees Example Carrier’s fleet.

      From

      Example Telematics Co. · Example Carrier’s ELD

      To

      Core 48213 · TruckerTech

      Reference

      TRK-214

   4. Intelligence · draftsIntelligencefor Example Broker

      Intelligence spots it: the ETA is 9:10 AM and the window ends at 8:00 AM. It proposes asking for Fri 9:00–11:00 AM.

      Why it’s safe It cites its sources, marks the inference as inference and proposes. Morgan decides.

   5. PersonMorgan K.Example Broker

      Morgan approves the fix.

      Why it’s safe Nothing outward ran before this approval.

   6. Automation · acts within authorityAutomationfor Example Broker

      Requests Fri 9:00–11:00 AM from Example Facility.

      From

      Core 48213 · TruckerTech

      To

      Example Scheduling Co. · Example Facility’s dock scheduling

      Reference

      REQ-7731

   7. Their system · Scheduling and appointmentsExample Scheduling Co.for Example Facility

      Example Facility confirms the later window. The appointment moves.

      Why it’s safe Still the facility’s decision, in its own system. The reference on the Core updates.

      From

      Example Scheduling Co. · Example Facility’s dock scheduling

      To

      Core 48213 · TruckerTech

      Reference

      APPT-0931 · rev 2

   8. Automation · acts within authorityAutomationfor Example Broker

      Automation tells the receiver and the shipper about the new window.

      Why it’s safe Within the notification rules Example Broker set. Each seat gets only its part.

      From

      Core 48213 · TruckerTech

      To

      Example Facility’s seat · TruckerTech

      Reference

      APPT-0931 · rev 2

   9. Automation · acts within authorityAutomationfor Example Broker

      Tells Example Shipper Co. the new window.

      From

      Core 48213 · TruckerTech

      To

      Example Shipper Co.’s seat · TruckerTech

      Reference

      SO-118204

   10. Automation · acts within authorityAutomationfor Example Carrier

       Updates the window on Riley M.’s phone.

       From

       Core 48213 · TruckerTech

       To

       Riley M.’s phone · TruckerTech

       Reference

       APPT-0931 · rev 2

   11. Automation · acts within authorityAutomationfor Example Carrier

       On Example Carrier’s canvas, its own Automation puts the new window on Riley M.’s phone and into Example Dispatch Suite.

       Why it’s safe Example Carrier’s own rules and connection make these writes. Example Broker’s approval reaches only Example Broker’s side.

       From

       Core 48213 · TruckerTech

       To

       Example Dispatch Suite · Example Carrier’s TMS

       Reference

       LD-5521 · rev 2

6. 6 Delivery: Arrived, said, photographed

   The phone notices the arrival and the driver confirms by voice. The proof of delivery is photographed, read by Intelligence and confirmed by a person.

   3 by people · 7 by TruckerTech · 2 of their own systems · 0 partners · 3 organizations

   1. Automation · acts within authorityAutomationfor Example Carrier

      Riley’s phone notices the truck has arrived and asks once, in large type.

      Why it’s safe The position is checked once against the stop, and only the result is kept. Where Riley has been is never stored.

   2. PersonRiley M.Example Carrier

      Riley confirms by voice: “yes”.

      Why it’s safe One word, hands free. It lands on the Core as Riley’s own confirmation.

   3. Automation · acts within authorityAutomationfor Example Carrier

      Records Arrived 9:12 AM at the stop; every permitted seat sees it.

      From

      Riley M.’s phone · TruckerTech

      To

      Core 48213 · TruckerTech

      Reference

      EVT-2201

   4. PersonRiley M.Example Carrier

      Riley photographs the signed receipt.

      Why it’s safe The photo goes to Core 48213 as it is taken, not days later.

      From

      Riley M.’s phone · TruckerTech

      To

      Core 48213 · TruckerTech

      Reference

      DOC-5530

   5. Intelligence · draftsIntelligencefor Example Carrier

      Intelligence classifies the photo as a proof of delivery and pulls out the fields, each with how sure it is.

      Why it’s safe It reads and proposes. Nothing is filed until a person confirms.

   6. PersonSam T.Example Carrier

      Sam T. checks the one inferred field and confirms.

      Why it’s safe Confirming is Sam’s act; the original photo stays with the Core.

   7. Automation · acts within authorityAutomationfor Example Carrier

      Files the POD with Example Dispatch Suite.

      From

      Core 48213 · TruckerTech

      To

      Example Dispatch Suite · Example Carrier’s TMS

      Reference

      LD-5521 · POD

   8. Automation · acts within authorityAutomationfor Example Carrier

      Shares the POD with Example Broker’s seat.

      From

      Core 48213 · TruckerTech

      To

      Example Broker’s seat · TruckerTech

      Reference

      DOC-5530

   9. Automation · acts within authorityAutomationfor Example Broker

      The POD reaches every seat allowed to see it and is filed in both TMSs.

      Why it’s safe Each write goes through that organization’s own connection and returns its reference.

      From

      Core 48213 · TruckerTech

      To

      Example TMS Co. · Example Broker’s TMS

      Reference

      BRK-77310 · POD

   10. Automation · acts within authorityAutomationfor Example Broker

       Shares the POD with Example Shipper Co.’s seat.

       From

       Core 48213 · TruckerTech

       To

       Example Shipper Co.’s seat · TruckerTech

       Reference

       DOC-5530

7. 7 Invoice: Proof lands, the invoice goes

   Within the broker’s billing rules, Automation sends the broker’s invoice to the shipper when proof lands, and prepares the carrier’s invoice.

   0 by people · 3 by TruckerTech · 2 of their own systems · 0 partners · 3 organizations

   1. Automation · acts within authorityAutomationfor Example Broker

      Proof landed, so Automation prepares Example Broker’s invoice to Example Shipper Co.

      Why it’s safe Within Example Broker’s billing rules: the amount comes from the accepted tender, and the POD goes with it.

      From

      Core 48213 · TruckerTech

      To

      Example TMS Co. · Example Broker’s TMS

      Reference

      INV-20931

   2. Automation · acts within authorityAutomationfor Example Broker

      And sends it. Nobody had to.

      Why it’s safe Example Broker’s billing rules authorize this send, so no one has to press it. Anything outside those rules waits for a person.

      From

      Example TMS Co. · Example Broker’s TMS

      To

      Example Shipper Co.’s seat · TruckerTech

      Reference

      INV-20931

   3. Automation · acts within authorityAutomationfor Example Carrier

      On Example Carrier’s canvas, its invoice to Example Broker is prepared from the signed rate confirmation.

      Why it’s safe Within Example Carrier’s billing rules. Where it goes next is Sam’s choice.

      From

      Core 48213 · TruckerTech

      To

      Example Dispatch Suite · Example Carrier’s TMS

      Reference

      INV-C-1187

8. 8 Factoring: One packet to the carrier’s own factor

   The carrier’s invoice, the POD and the rate confirmation go as one packet through the carrier’s own factoring connection, and funding status flows back.

   1 by people · 3 by TruckerTech · 1 of their own systems · 1 partner · 2 organizations

   1. Intelligence · draftsIntelligencefor Example Carrier

      Intelligence assembles one packet: the invoice, the POD and the rate confirmation, and checks that they agree.

      Why it’s safe It prepares and checks. Example Carrier’s billing rules leave submitting to a person, so Sam decides.

   2. PersonSam T.Example Carrier

      Sam submits it for funding.

      Why it’s safe Money moves only between Example Carrier and its own factor, never through TruckerTech.

   3. Automation · acts within authorityAutomationfor Example Carrier

      Sends the packet through Example Carrier’s factoring connection.

      From

      Core 48213 · TruckerTech

      To

      Example Factoring Co. · Example Carrier’s factoring connection

      Reference

      SUB-60218

   4. Partner · Factoring and credit approvalExample Factoring Co.for Example Carrier

      Example Factoring Co. acknowledges and returns its own reference, FAC-90314.

      Why it’s safe Example Broker never sees the submission or its status. It belongs to Example Carrier’s seat.

      From

      Example Factoring Co. · Example Carrier’s factoring connection

      To

      Example Carrier’s seat · TruckerTech

      Reference

      FAC-90314

   5. Partner · Factoring and credit approvalExample Factoring Co.for Example Carrier

      Funding status flows back into Example Carrier’s view of Core 48213: approved for funding.

      Why it’s safe Shown exactly as the factor reported it, with its source and age.

      From

      Example Factoring Co. · Example Carrier’s factoring connection

      To

      Example Carrier’s seat · TruckerTech

      Reference

      FAC-90314 · approved

   6. Automation · acts within authorityAutomationfor Example Carrier

      Writes the factoring reference into Example Dispatch Suite.

      From

      Core 48213 · TruckerTech

      To

      Example Dispatch Suite · Example Carrier’s TMS

      Reference

      LD-5521 · FAC-90314

Illustrative · synthetic data. Every company, person, system and reference here is fictional, and every count on this page is counted from these steps. See also Automation, Intelligence and the Exchange.