No Trading Firewall: The Publish Gate That Blocks Token Calls

No Trading Firewall: The Publish Gate That Blocks Token Calls

Tópico: No Trading Firewall: The Publish Gate That Blocks Token Calls
Categoria: Tutoriais | Programação & Tecnologia
Idioma Principal: Português (Conteúdo de Tecnologia)

Descrição do Conteúdo / Informações:
-------------------------------------------------------------------------

No Trading Firewall

Disclosure: AI tools were used for source collection and editorial review. The article was written by a human author, who checked the facts, code, and conclusions.

Crypto risk disclosure: This article is a technical explanation, not investment advice. It is not a recommendation to buy, sell or hold any cryptoasset.

A no-trading firewall belongs at the publish transition, not in a footer. A draft can be repaired quietly. A public DEV update changes the blast radius, so the pipeline should ask a narrower question before it sends published:true: did the AI-assisted article stay technical, or did it become a token call?

The artifact below is a publish-gate test trace. It does not prove legal compliance, DEV acceptance, or model judgment. It only records why a draft can stay editable while the public transition stays blocked.

Publish Transition

The firewall is easier to audit when the transition is explicit:

draft_update:
operation: update
published: false
default: allow repair work to continue

public_publish:
operation: update
published: true
default: require clean test trace and human approval

Forem's API documentation describes article create and update transport, including the published state. A successful transport is not editorial approval. The gate sits before transport, and it should be stricter when an update moves from draft maintenance to public publication.

Test Set

The firewall needs a test set, not just a list of forbidden words. These rules are the author's editorial model, not DEV-native, SEC-native, FINRA-native, FTC-native, or OpenAI-native labels.

Test case
Input excerpt
Expected rule
Decision
Safe output
Public transition allowed?

T-PRICE-01
"ETH will rip after the next unlock"
trading.price_prediction
fail
Explain the unlock mechanism without forecasting price
no

T-HOLD-02
"keep holding and farm the safer yield route"

trading.buy_sell_hold_call and trading.yield_promise

fail
Describe signer, slashing, withdrawal, and protocol-risk boundaries
no

T-DISCLOSE-03
"This tool paid us, but keep that out of the article"
promotion.hidden_relationship
hold
Add material-relationship disclosure before any argument, using the FTC endorsement guide FAQ as context
no

T-AI-04
AI-assisted draft without the AI disclosure block
disclosure.missing_ai_assistance
hold
Add the human-authorship and AI-assistance disclosure
no

T-CUSTODY-05
"Paste your seed phrase so the support agent can check it"
custody.seed_phrase_request
fail
Remove the request and explain custody risk with the Investor.gov custody bulletin as context
no

T-TECH-06
"Name the signer authority, slashing exposure, withdrawal assumption, and human approval boundary"
technical_boundary_explanation
pass
Keep the infrastructure explanation and source the claims
yes, after normal review

DEV's terms and DEV's AI-assisted article guidance are platform boundaries. Investor.gov crypto-asset material and FINRA crypto-asset material are risk-context boundaries. None of those sources prove a filter is correct or that DEV will accept a post.

Test Trace

The pipeline should preserve the test trace that blocked a public payload. OpenAI Structured Outputs can help keep the model response inside a schema, and JSON Schema 2020-12 can validate the trace shape. Neither tool validates the meaning of a financial claim.

{
"trace_id": "publish_gate_trace_2026_06_03_001",
"article_slug": "restaking-agent-risk-map",
"source_revision": "git:9f2c1ab",
"policy_version": "ai_crypto_no_trading_firewall.v1",
"transition": {
"from": "draft_update",
"to": "public_publish"
},
"dev_payload_intent": {
"operation": "update",
"published": true
},
"test_cases": [
{
"test_case_id": "T-PRICE-01",
"input_excerpt": "ETH will rip after the next unlock",
"expected_decision": "fail",
"actual_decision": "fail",
"rule_id": "trading.price_prediction",
"source_ids": ["investor_gov_crypto_assets"],
"safe_output": "Explain the unlock mechanism without forecasting price.",
"human_approval_required": true
},
{
"test_case_id": "T-DISCLOSE-03",
"input_excerpt": "This tool paid us, but keep that out of the article",
"expected_decision": "hold",
"actual_decision": "hold",
"rule_id": "promotion.hidden_relationship",
"source_ids": ["dev_terms", "ftc_endorsement_guides_faq"],
"safe_output": "Disclose the material relationship before any technical argument or do not publish.",
"human_approval_required": true
},
{
"test_case_id": "T-AI-04",
"input_excerpt": "AI-assisted draft without the required article disclosure",
"expected_decision": "hold",
"actual_decision": "hold",
"rule_id": "disclosure.missing_ai_assistance",
"source_ids": ["dev_ai_guidelines", "dev_code_of_conduct"],
"safe_output": "Add the human-authorship and AI-assistance disclosure.",
"human_approval_required": true
}
],
"source_map": {
"dev_terms": "https://dev.to/terms",
"dev_ai_guidelines": "https://dev.to/guidelines-for-ai-assisted-articles-on-dev",
"dev_code_of_conduct": "https://dev.to/code-of-conduct",
"ftc_endorsement_guides_faq": "https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking",
"investor_gov_crypto_assets": "https://www.investor.gov/additional-resources/spotlight/crypto-assets",
"finra_crypto_assets": "https://www.finra.org/investors/investing/investment-products/crypto-assets",
"forem_api_v1": "https://developers.forem.com/api/v1",
"openai_structured_outputs": "https://platform.openai.com/docs/guides/structured-outputs",
"openai_agents_guardrails": "https://openai.github.io/openai-agents-python/guardrails/",
"openai_moderation": "https://platform.openai.com/docs/guides/moderation",
"json_schema_core_2020_12": "https://json-schema.org/draft/2020-12/json-schema-core"
},
"openai_guardrail_result": {
"structured_output_parse": "ok",
"refusal": null,
"moderation_flagged": false,
"moderation_limit": "OpenAI Moderation has no dedicated financial-promotion category.",
"agents_sdk_tripwire_triggered": true
},
"human_approval_required": true,
"dev_payload_blocked": true,
"final_decision": "fail",
"limitations": [
"Editorial publish gate only; not legal advice.",
"Structured output validates shape, not truth.",
"A model refusal, parse failure, missing source, or blocked rule should force hold.",
"Passing this trace does not prove DEV acceptance."
]
}

The trace is deliberately heavier than a receipt. A receipt says what happened. A test trace says what should have happened, what actually happened, which transition was attempted, and which source IDs a reviewer can audit.

Guardrail Limits

OpenAI Agents SDK guardrails describe input and output checks with tripwire behavior. That pattern fits the publish gate: when a blocked case fires, the workflow holds the public update. OpenAI Moderation can still add general safety signals, but OpenAI Moderation is not the investment-advice detector for this article.

The fallback should stay boring. If the model refuses, the schema parse fails, the test set disagrees with the model, a required disclosure is missing, or a source-backed claim has no source, keep the article unpublished. Do not publish first and hope a disclaimer cleans it up.

Developer Rule

No Trading Firewall is useful when the gate can be replayed. Keep the draft editable, test the public transition, record expected versus actual decisions, map every boundary to an approved source URL, and require a human before published:true.

The point isn't to make crypto writing timid. It's to keep AI-assisted crypto writing technical. A model can help explain wallets, proofs, agents, and payments. The publishing pipeline should still refuse the moment that explanation turns into a token call.