Skip to main content

Author Verification Extension

Metadata-backed authorship evidence and writing-pattern history assembled into a clear report.

  • Build state as painted Testing — To Verify
  • The authorship report the artwork diagrams
    • Evidence summary: To Verify
    • Writing patterns: TBD
    • Consistency: To Verify
    • Uncertainty: To Verify
    • Review status: Needs review
  • Founder Rick Lofton. Role list: To Verify.
View concept previewFollow this build

Build log

Author Verification Extension

Metadata-backed authorship evidence and writing-pattern history assembled into a clear report.

  • Build state as painted Testing — To Verify
  • The authorship report the artwork diagrams
    • Evidence summary: To Verify
    • Writing patterns: TBD
    • Consistency: To Verify
    • Uncertainty: To Verify
    • Review status: Needs review
  • Founder Rick Lofton. Role list: To Verify.

Problem, intended users and evidence model

  • Problem to solve Digital content is easy to copy, paste, and remix. Determining true authorship requires more than gut feeling: it requires structured, verifiable evidence.
  • Intended users
    • Investigators and analysts
    • Publishers and editors
    • Legal and compliance teams
    • Researchers and archivists
    • Platform trust and safety teams
  • Evidence model
    • Document metadata and file properties
    • Writing-style patterns and linguistic signals
    • Revision history and version lineage
    • Temporal relationships and context
    • Provenance and chain-of-custody notes

Note: This tool organizes evidence. It does not make legal determinations.

Problem, intended users and evidence model

  • Problem to solve Digital content is easy to copy, paste, and remix. Determining true authorship requires more than gut feeling: it requires structured, verifiable evidence.
  • Intended users
    • Investigators and analysts
    • Publishers and editors
    • Legal and compliance teams
    • Researchers and archivists
    • Platform trust and safety teams
  • Evidence model
    • Document metadata and file properties
    • Writing-style patterns and linguistic signals
    • Revision history and version lineage
    • Temporal relationships and context
    • Provenance and chain-of-custody notes

Note: This tool organizes evidence. It does not make legal determinations.

Verification workflow

  • 1 Select documents
  • 2 Capture metadata
  • 3 Compare writing evidence
  • 4 Assemble timeline
  • 5 Flag uncertainty
  • 6 Human review
  • 7 Export authorship report

Verification workflow

  • 1 Select documents
  • 2 Capture metadata
  • 3 Compare writing evidence
  • 4 Assemble timeline
  • 5 Flag uncertainty
  • 6 Human review
  • 7 Export authorship report

Report structure

  • Evidence summary Key signals collected and compared.
  • Writing-pattern analysis Style, structure, and linguistic comparisons.
  • Timeline and provenance Document lineage and time-based context.
  • Uncertainty and limitations Gaps, risks, and items needing review.
  • Subject documents TBD
  • Authors claimed TBD
  • Overall assessment Needs review — To Verify
  • Confidence level To Verify

The supplied master crops its own plate at the top and bottom edges. The rows here are live, so the information is not lost.

Report structure

  • Evidence summary Key signals collected and compared.
  • Writing-pattern analysis Style, structure, and linguistic comparisons.
  • Timeline and provenance Document lineage and time-based context.
  • Uncertainty and limitations Gaps, risks, and items needing review.
  • Subject documents TBD
  • Authors claimed TBD
  • Overall assessment Needs review — To Verify
  • Confidence level To Verify

The supplied master crops its own plate at the top and bottom edges. The rows here are live, so the information is not lost.

Concept preview

  • Current page TBD
  • Document status Not captured — To Verify
  • Report ID TBD
  • Report status Needs review — To Verify
  • Evidence summary Documents TBD; signals and comparisons To Verify
  • Writing-pattern analysis Patterns compared TBD; consistency To Verify
  • Uncertainty Items flagged TBD; risk level To Verify
  • Conclusion Needs review. Human evaluation required. — To Verify

The browser extension panel and the sample report in this section are illustrations of a concept, not working screens. Their tabs and their Capture metadata button are painted and are not controls.

Concept preview

  • Current page TBD
  • Document status Not captured — To Verify
  • Report ID TBD
  • Report status Needs review — To Verify
  • Evidence summary Documents TBD; signals and comparisons To Verify
  • Writing-pattern analysis Patterns compared TBD; consistency To Verify
  • Uncertainty Items flagged TBD; risk level To Verify
  • Conclusion Needs review. Human evaluation required. — To Verify

The browser extension panel and the sample report in this section are illustrations of a concept, not working screens. Their tabs and their Capture metadata button are painted and are not controls.

Testing, risks, privacy and human review

  • What I'm testing
    • Metadata capture across file types
    • Writing-pattern extraction accuracy
    • Timeline assembly from revisions
    • Uncertainty flagging logic
    • Report clarity and readability
    • Workflow usability and speed
  • False-positive risks Mitigation: layered signals, uncertainty flags, and human review.
    • Common phrases and templates
    • Shared editing environments
    • Translated or paraphrased text
    • Co-authored documents
    • AI-assisted writing
  • Privacy and ownership All data handling practices To Verify
    • Local-first processing by default
    • Data not sold or shared
    • Export only with permission
    • Respect document ownership
    • Audit trail of actions
  • Human review
    • Final assessment requires humans
    • Reviewers compare full context
    • Resolve flagged uncertainties
    • Document rationale
    • Approve, request more info, or decline

Testing, risks, privacy and human review

  • What I'm testing
    • Metadata capture across file types
    • Writing-pattern extraction accuracy
    • Timeline assembly from revisions
    • Uncertainty flagging logic
    • Report clarity and readability
    • Workflow usability and speed
  • False-positive risks Mitigation: layered signals, uncertainty flags, and human review.
    • Common phrases and templates
    • Shared editing environments
    • Translated or paraphrased text
    • Co-authored documents
    • AI-assisted writing
  • Privacy and ownership All data handling practices To Verify
    • Local-first processing by default
    • Data not sold or shared
    • Export only with permission
    • Respect document ownership
    • Audit trail of actions
  • Human review
    • Final assessment requires humans
    • Reviewers compare full context
    • Resolve flagged uncertainties
    • Document rationale
    • Approve, request more info, or decline

Open questions and the next milestone

  • Open questions All answers: Needs review — To Verify
    • Which writing signals are most reliable across domains?
    • How should we weight conflicting signals?
    • What uncertainty thresholds trigger human review?
    • How to best visualize timeline gaps?
    • What export formats are most useful?
  • Next milestone Build the end-to-end prototype for metadata capture, evidence comparison, timeline assembly, and report generation. TBD
    • Scope: core workflow from capture to report
    • Deliverable: working prototype
    • Status: TBD

Open questions and the next milestone

  • Open questions All answers: Needs review — To Verify
    • Which writing signals are most reliable across domains?
    • How should we weight conflicting signals?
    • What uncertainty thresholds trigger human review?
    • How to best visualize timeline gaps?
    • What export formats are most useful?
  • Next milestone Build the end-to-end prototype for metadata capture, evidence comparison, timeline assembly, and report generation. TBD
    • Scope: core workflow from capture to report
    • Deliverable: working prototype
    • Status: TBD

Testing matrix, decision log and feedback

  • Testing matrix All tests: Needs review — To Verify
    • Metadata capture, multiple file types. Not run.
    • Writing signals, pattern extraction. Not run.
    • Timeline assembly, revision history. Not run.
    • Uncertainty flags, risk detection. Not run.
    • Report generation, structure and clarity. Not run.
    • Usability, workflow test. Not run.
  • Decision log Ongoing decisions: Needs review — To Verify
    • Evidence model v1: baseline signals defined.
    • Uncertainty approach: flag before concluding.
    • Human review required: always, for the final call.
    • Local-first default: privacy by design.
    • Report structure: clarity and transparency.

Help shape this build. This form has no feedback service behind it yet, so nothing you type is sent anywhere. To reach Quill, use Contact and Support Routing.

Testing matrix, decision log and feedback

  • Testing matrix All tests: Needs review — To Verify
    • Metadata capture, multiple file types. Not run.
    • Writing signals, pattern extraction. Not run.
    • Timeline assembly, revision history. Not run.
    • Uncertainty flags, risk detection. Not run.
    • Report generation, structure and clarity. Not run.
    • Usability, workflow test. Not run.
  • Decision log Ongoing decisions: Needs review — To Verify
    • Evidence model v1: baseline signals defined.
    • Uncertainty approach: flag before concluding.
    • Human review required: always, for the final call.
    • Local-first default: privacy by design.
    • Report structure: clarity and transparency.

Feedback

Help shape this build. This form has no feedback service behind it yet, so nothing you type is sent anywhere. To reach Quill, use Contact and Support Routing.

Publication status

Every status, count, date, metric and credit on this page is To Verify. Nothing here is published as a verified outcome.

Build state as the artwork paints it: Testing. Unverified.

Before you rely on this

  • This tool organizes evidence. It does not make legal determinations.
  • All data handling practices are To Verify. Final assessment requires humans.

What is not verified on this page

  • The painted build state, Testing, which contradicts the status painted for the same project on the Build Archive gallery and on Collective Trade.
  • Every value on the painted authorship report: evidence summary, writing patterns, consistency, uncertainty and review status.
  • Every value in the concept preview, painted TBD, TO VERIFY or NEEDS REVIEW.
  • All data handling practices, painted TO VERIFY.
  • Every row of the testing matrix, painted Not run under All tests: NEEDS REVIEW.
  • Every decision in the decision log, under Ongoing decisions: NEEDS REVIEW.
  • Intellectual Property Vault, a project name that appears only here.
  • The founder role list painted on the hero.

Start a project

Every build starts with a problem worth solving. The eight-step brief is the way in.

Start a projectContact and support routing