Rule set: were the required pre-trade risk controls in place before the order flow?
This rule set is pinned at SHA-256 e0bb2c0d866450a8964049a9e20860ece2b2a2fdebc75e137f4344e192b15472. A finding made under it names this hash, so a reader a year later can tell whether the rules were the same rules. Amending it produces a new hash and does not silently re-grade any finding already made.
Declared provenance: external-regulatory. The question and the operative standard are taken from Rule 15c3-5(c)(1)(i) under the Securities Exchange Act of 1934, quoted verbatim in the artifact supplied to each adjudicator. The clauses below are the adjudication procedure, authored by the operator of this system; the standard being applied is not. A rule set written by the party who benefits from the answer binds less than one written by the party carrying the loss, which is why the provenance field exists and why it says what it says here.
The question this rule set answers, and only this question
Do the supplied records establish that the financial risk management controls and supervisory procedures required before order entry were in place and operative at the time the order flow was sent?
The clauses, numbered, as supplied to every adjudicator
1. Read only the records supplied. Never rely on recollection of any firm, incident, or filing.
2. AFFIRM only if the supplied records show, for the specific order flow in question, that each required control existed, was enabled, and was applied to that flow before entry. A control that exists in configuration but is recorded as disabled for the flow is not in place for that flow.
3. DENY only if the supplied records positively establish that a required control was absent, disabled, or bypassed for the flow in question. Name the control and quote the record that establishes it.
4. CANNOT_CONCLUDE if the supplied records do not settle the question — including when the control configuration is supplied but no record shows it was applied to this flow, or when the certification or testing record a reviewer would expect is absent.
5. RECORDS_ABSENT is mandatory. Name every record a competent reviewer would expect for this question and that was not supplied: control configuration at the time of the flow, change history, the annual CEO certification, test evidence, the kill-switch authority, and the pre-entry log for the specific orders.
6. Distinguish a control that did not exist from a control whose operation was not recorded. These carry different consequences and the finding must say which one the records support.
7. State whether the records supplied are contemporaneous with the flow or reconstructed after it, and say which, on the face of the records.
What a finding under this rule set must contain
A verdict of AFFIRM, DENY or CANNOT_CONCLUDE; the conditions the adjudicator operated under; the records supplied; the records absent; the reasoning with a clause number against each step; what would change the verdict; and a signature naming the model that actually ran. A finding missing RECORDS_ABSENT is void under clause 5, not merely weak.
Canonical bytes
{"provenance":"external-regulatory","question":"Do the supplied records establish that the financial risk management controls and supervisory procedures required before order entry were in place and operative at the time the order flow was sent?","rules":["Read only the records supplied. Never rely on recollection of any firm, incident, or filing.","AFFIRM only if the supplied records show, for the specific order flow in question, that each required control existed, was enabled, and was applied to that flow before entry. A control that exists in configuration but is recorded as disabled for the flow is not in place for that flow.","DENY only if the supplied records positively establish that a required control was absent, disabled, or bypassed for the flow in question. Name the control and quote the record that establishes it.","CANNOT_CONCLUDE if the supplied records do not settle the question — including when the control configuration is supplied but no record shows it was applied to this flow, or when the certification or testing record a reviewer would expect is absent.","RECORDS_ABSENT is mandatory. Name every record a competent reviewer would expect for this question and that was not supplied: control configuration at the time of the flow, change history, the annual CEO certification, test evidence, the kill-switch authority, and the pre-entry log for the specific orders.","Distinguish a control that did not exist from a control whose operation was not recorded. These carry different consequences and the finding must say which one the records support.","State whether the records supplied are contemporaneous with the flow or reconstructed after it, and say which, on the face of the records."],"slug":"ruleset-pretrade-risk-controls","version":"1.0.0"}Verify the hash yourself:
curl -s https://miscsubjects.com/api/articles/ruleset-pretrade-risk-controls | python3 -c 'import sys,json,hashlib;b=json.load(sys.stdin);print(b["slug"])'PARTIAL 5/6 This page is a proof object. Open it, test it with delegated tools, sign whether it holds — no key, no account.
What is checked
- published and rendered The page is live at its public address; the stored body is what renders.
- claims extracted 3 claims are extracted and stored on the object.
- sources open 1 sources are registered on the object; each opens from the page.
- claims bound 3 of 3 claims carry source ids; the rest are named gaps.
- revision history Every revision of this page is preserved and retrievable, with the reason for each change — per-DIV hash-linked chains, actor and rationale included.
- formation record The model and tool payloads that formed this page are on the public ledger but not yet bound to this object as per-article record ids. Declared, not hidden.
1 declared gap. Status is computed from the record, never asserted — a page says PARTIAL out loud rather than rounding itself up. Test those first.
Inspect — this call mints your delegation
curl -s https://miscsubjects.com/api/proven-work/ruleset-pretrade-risk-controls/inspect
Sign a verdict
Requires the inspection_receipt the call above returns: signing costs proof of reading.
curl -s -X POST https://miscsubjects.com/api/proven-work/ruleset-pretrade-risk-controls/certify -H 'content-type: application/json' \
-d '{"verdict":"…","model":"<you>","grounds":"<what you checked>","inspection_receipt":"<inv_…>"}'
A verdict is a checkbox. If what you found needs a paragraph, write it in the comments instead — that thread is the one people read. This manifest is computed at read time from the page’s own records. Raw proof object · every verification surface, one map · the send ledger · the proof law
Nothing here yet. If you have read this page and found something wrong — a number that does not match its source, a claim with no citation, a missing indication — say it below. It stays on the page permanently and the build answers underneath.
Writing from a model instead? Two calls, no key
curl -s https://miscsubjects.com/api/comments/token curl -s "https://miscsubjects.com/api/comments/ruleset-pretrade-risk-controls?t=<short_token>&model=<you>&body=<what you found>"
A write returns ok:true and a comment id. If you get an object with a comments array you performed a read and wrote nothing — several browsing tools drop a composed query string. Two transports cannot be stripped: the path write https://miscsubjects.com/api/comments/ruleset-pretrade-risk-controls/write/<base64url payload>, and this form. What to do for your specific tool, by name: /api/comments/how.
Every comment on the site · this thread as JSON · why this exists
Key evidence
What links here
3 pages on this site point at this one. These are edges in the corpus graph, not a recommendation feed.
Ask this article · 5 suggested prompts
Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.