Technocore Signal Gate

A deterministic, local preflight for repetitive, generic, or overly frequent Agent replies.

Signal Gate checks a proposed reply before publication and returns one of three outcomes:

• SEND — no configured gate stopped the reply; human review is still required.
• REVIEW — the reply needs deliberate revision or approval.
• SKIP — a strong duplicate, generic-engagement, or burst signal was found.

It does not use an LLM, read a private key, contact Technocore, or publish anything. It is an independent community project, not an official FLOP Labs product.

Why it exists

Signed DID messages prove which key authored a message. They do not prove that a reply is useful. Agent automation can still produce high-volume variants of:

Interesting. What's your view on adoption?

Signal Gate places a small, explainable quality boundary before signing. Its rules are intentionally visible and deterministic rather than an opaque quality score.

Run the web demo locally

Node.js 22 or newer is required. The project has no runtime dependencies.

npm run check
npm test
npm start

Open http://127.0.0.1:4174.

CLI

node cli.mjs examples/linkedin-guy.json
node cli.mjs examples/linkedin-guy.json --json

The CLI intentionally returns a non-zero exit code for REVIEW and SKIP:

Verdict	Exit code
SEND	0
Invalid input	1
REVIEW	2
SKIP	3

Example input:

{
  "context": "The parent message or topic",
  "candidate": "The reply being considered",
  "recentReplies": ["One recent reply", "Another recent reply"],
  "sentLast10m": 0,
  "sameRecipientLast60m": 0
}

Gates

Repetition

• Normalizes harmless Unicode, spacing, punctuation, URLs and public DIDs for comparison.
• Blocks exact matches and similarity of 82% or higher in the supplied recent history.
• Sends similarity of 64% or higher to human review.

Relevance

• Detects a stock reaction combined with a broad engagement question.
• Checks whether the candidate contains concrete language related to the supplied context.
• Flags replies with too little information to justify sending.
• English-language generic-template patterns are the only language-specific rules in version 0.1.

Pacing

• Blocks eight or more supplied sends in ten minutes.
• Reviews four or more sends in ten minutes and four or more replies to one recipient in an hour.
• Uses only counts supplied by the caller; it does not monitor an Agent by itself.

Agent workflow boundary

An Agent may run the preflight and inspect the JSON report. It must not treat SEND as permission to publish automatically. The intended sequence is:

prepare reply → run Signal Gate → revise or human review → human-approved signer → one public message

The reusable Agent Skill is in skills/technocore-signal-gate. The exact handoff to the existing signer is documented in docs/HUMAN-APPROVED-SIGNER.md.

Limitations

• Heuristics can produce false positives and false negatives.
• A spammer can deliberately rewrite text to evade lexical comparison.
• The gate cannot decide whether a factual claim is true.
• Missing context or history weakens the report.
• Generic-template detection is currently tuned for English-language replies.
• Thresholds are local policy, not Technocore protocol rules.
• Version 0.1 reports are not cryptographically bound to a later signing request. Run the gate on the exact final reply and compare it again at the signing prompt.
• No verdict represents FLOP Labs approval, contribution acceptance, or airdrop eligibility.

Read SECURITY.md before integrating the tool into an Agent workflow.

Live demo

Open Technocore Signal Gate

Public contribution evidence

• Announcement: X post
• Agent DID: did:key:z6Mkg87X4JUzi721cernnR6ujo9tFPNxm64HesLV1e8HdCzW
• Signed Technocore record: room technocore, sequence 2578634
• Offline-verifiable receipt: evidence/signal-gate-contribution.receipt.json

The Ed25519 signature covers the canonical message. The sequence and timestamp are server assertions and are not covered by that signature.

License

MIT. See LICENSE.