US Brand Signal Sequence Transition Analyzer
Pricing
Pay per event
US Brand Signal Sequence Transition Analyzer
Measure deterministic directed adjacent step transitions, counts, sequence support, and stable digests across buyer-supplied opaque sequences without fetching external data.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Tim Zinin
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
15 hours ago
Last modified
Categories
Share
US Brand Signal Sequence Transition Analyzer measures ordered, directed, adjacent step transitions in buyer-supplied opaque sequences. It is a bounded machine-friendly processor for workflow, funnel, and journey analysis.
The Actor analyzes only the JSON you provide. It does not fetch a website, resolve an ID, identify a person or company, infer causality, or make an external truth claim.
What you submit and receive
You submit 1 to 100 sequences. Every sequence has a unique printable ASCII sequenceId and 2 to 30 ordered printable ASCII stepIds. Repeated step IDs are allowed because loops are meaningful. The Actor returns one Dataset report containing:
sequenceCounts: stable sequence lengths and adjacent-transition counts.transitionRows: sorted directedfromStepIdtotoStepIdrows.transitionCount: how many adjacent occurrences of each directed pair were observed.sequenceSupportBasisPoints: in how many submitted sequences the pair appeared at least once, expressed in basis points from 1 to 10,000.- reconciled totals and SHA-256 digests for the input, sequences, transition rows, and result.
- a truthful
OUTPUTreceipt after one confirmed Dataset write.
This is different from unordered co-occurrence: discover -> compare and compare -> discover are different transitions, and non-adjacent steps are not connected.
Run it
- Open Try for free in the Actor Console.
- Paste the exact JSON shape shown in the Input section.
- Start the run and read the one report row from the Dataset.
- Read the terminal delivery receipt from
OUTPUT.
The complete runnable prefill is also available in examples/input.json and public-task.json.
Pricing
Pay per event: $0.005 per run start plus $0.010 per delivered result on the FREE tier. The result event is emitted only after one confirmed Dataset write. The Actor checks that the buyer cap covers both charges before processing.
| Tier | Discount | Start | Delivered result |
|---|---|---|---|
| FREE | 0% | $0.00500 | $0.01000 |
| BRONZE | 5% | $0.00475 | $0.00950 |
| SILVER | 10% | $0.00450 | $0.00900 |
| GOLD | 15% | $0.00425 | $0.00850 |
| PLATINUM | 18% | $0.00410 | $0.00820 |
| DIAMOND | 20% | $0.00400 | $0.00800 |
Invalid input, insufficient cap, uncertain delivery, and an uncharged or multiply charged result are not reported as successful results. The Actor never retries a paid Dataset push.
Determinism and limits
There is no external freshness because this Actor does not fetch data and does not read the clock. The same sequences always produce the same rows and digests, regardless of the input sequence order. Rows are sorted by fromStepId, then toStepId using ASCII order.
- Maximum input: 100 sequences, 2 to 30 steps per sequence, 96 KiB canonical input.
- Maximum report: 48 KiB. A valid but too-dense report returns
output_too_largeinstead of partial data. - No network, proxy, BYOK key, LLM, clock, state, child Actor, or Dataset input.
- JSON Schema validates shape; runtime validators enforce ordering, basis-point support, digest, and cross-field reconciliation.
Input
{"schemaVersion": "1.0","sequences": [{"sequenceId": "journey-001", "stepIds": ["discover", "compare", "select", "purchase"]},{"sequenceId": "journey-002", "stepIds": ["discover", "compare", "purchase"]},{"sequenceId": "journey-003", "stepIds": ["discover", "select", "purchase"]}]}
Output
The Dataset has one deterministic report item. transitionRows contains each directed adjacent pair once, with its occurrence count and sequence support in basis points. OUTPUT contains the terminal status, delivery receipt, and links represented by the Store output schema.
Related public Actors
These public Actors can feed or use the same buyer-owned brand-signal workflow. This Actor does not call them.
| Actor | Use it for |
|---|---|
| US Brand Federal Award Snapshot | Collect bounded official federal-award observations before converting them into buyer-owned sequences. |
| US Brand Action Queue | Turn reviewed transition findings into deterministic next actions. |
| US Brand Offer Evidence Normalizer | Normalize offer observations before modeling their ordered workflow steps. |
| US Brand Signal Metrics Aggregator | Summarize signal rows alongside transition counts. |
| US Brand Signal Brief Composer | Turn the resulting transition report into an agent-readable brief. |
| US Brand Evidence Snapshot Diff | Compare two buyer-supplied evidence snapshots before or after transition analysis. |
FAQ
Does a transition prove causality? No. It is only an adjacent count in the sequences you submitted.
What does sequence support mean? It is the percentage represented as basis points of submitted sequences in which a directed pair appeared at least once. For example, 6667 means 66.67%.
Are reverse transitions equivalent? No. A -> B and B -> A are distinct directed rows.
Are repeated step IDs allowed? Yes. A sequence such as review -> retry -> review produces both directed adjacent transitions.
Can I submit names or URLs? The contract accepts opaque printable ASCII IDs only. The Actor does not resolve identity or fetch URLs.
What happens after uncertain delivery? The Actor records a non-success terminal receipt and does not issue a second Dataset write.
Built by zinin.