Person tag · Coming Soon
BT — Automation pattern
Will research positive evidence of automation and explain exactly what was observed.
Templates, repetition, timing, or missing human activity alone are not proof of a bot.
Validation · Research proposal
Validation required before release
This capability is not available yet. It needs a working method and independent testing before release.
Use this tag
Research proposal. This code is not issued and has no downloadable checker yet.
See How it works for its intended job. Help improve this tag to contribute or follow its progress.
Baseline job
Research positive evidence of automation without inferring it from absent human activity.
What the tag can claim
Proposed automation observation; cannot establish automation from style alone.
Method and evidence
- Candidate timing and duplicate-construction indicators require validation; no detector exists.
- Development · standard v0.1.0
- Unmeasured proposal.
Input
Positive, consented evidence within a defined observation scope.
Output
A versioned tag record with subject binding, method, evidence, limitations, and a result state.
Supported scope
- Research proposal only
Limits
- Templates, repetition, timing, and learned writing patterns are not automation proof
- Absent human evidence never becomes a bot verdict
- Does not ship if indicators cannot separate ordinary human behavior
Accuracy and validation
Not independently release validated.
Cost and access
Free personal workflow. No paid detector, evidence, or verification gate.
Privacy
This catalogue does not evaluate your content. The personal reference implementation uses local services; detected redaction can miss sensitive information.
Dependencies
- Versioned claim and evidence contract
- Independent review for this tag
- Accessible presentation and a clear failure state
Failure behavior
A failed or unsupported check must not become a finding. A problem with this tag must not disable unrelated tags.
Who owns the outcome
Maintainers own implementation; independent reviewers own validation; the product owner accepts release.
Before release
Publish agreed acceptance criteria, run independent validation, and verify the complete user workflow before release.
Tag enhancements in scope
- F-086 — No telemetry, no analytics, no phone-home — in the extension or the services. Keep local evaluation free of automatic telemetry; separate any approved in-house research contribution under N-011. Scope record; not an implementation claim.
- F-083 — The governing rule: a provenance signal may raise toward PA or FA but may never lower a tag toward a human-negative verdict. Absence of human signal produces UNK, never FA. Specify and deliver the governing rule: a provenance signal may raise toward PA or FA but may never lower a tag toward a human-negative verdict. Absence of human signal produces UNK, never FA. Scope record; not an implementation claim.
Shared tag capabilities
- F-001 — Assertion envelope schema, JSON Schema 2020-12. Specify and deliver assertion envelope schema, JSON Schema 2020-12. Scope record; not an implementation claim.
- F-003 — Signal registry, 22 registered IDs with version suffixes. Specify and deliver signal registry, 22 registered IDs with version suffixes. Scope record; not an implementation claim.
- F-004 — Abstention as a first-class state — UNK. Specify and deliver abstention as a first-class state — UNK. Scope record; not an implementation claim.
- F-005 — Per-tag confidence floors. Specify and deliver per-tag confidence floors. Scope record; not an implementation claim.
- F-007 — Content-free assertion records. Return hashes, offsets, and metadata without embedding evaluated text Scope record; not an implementation claim.
- F-008 — Signed assertion integrity. Sign an exact canonical tag record with an identified key Scope record; not an implementation claim.
- F-009 — Cost-to-defeat ladder — statistical / behavioural / structural / cryptographic. Specify and deliver cost-to-defeat ladder — statistical / behavioural / structural / cryptographic. Scope record; not an implementation claim.
- N-005 — Label dispute, correction, and supersession workflow. Specify and deliver label dispute, correction, and supersession workflow. Scope record; not an implementation claim.
- N-006 — Versioned regression checks and revalidation triggers. Specify and deliver versioned regression checks and revalidation triggers. Scope record; not an implementation claim.
References
Scope record T-BT. Preserved scope is not implementation evidence.