Skip to content

Align public messaging to Jan 6, 2027 BlockSiFr launch #47

Description

@blocksifrdev

Repository rules prevented the automated messaging commit because this protected repo requires verified signatures / Code Scanning compliance.

Required public messaging:

  • Public launch: January 6, 2027
  • Early access is open now for interested organizations, builders, design partners, and strategic partners
  • Your AI has credentials. BlockSiFr gives it boundaries.
  • Same identity. Same permission. Different consequence. Different decision.
  • Category: Execution Control Infrastructure
  • Core intelligence: Consequence Intelligence
  • CTA: Put an action under Control.

TTP should remain positioned as a protocol-level trust mechanic beneath BlockSiFr Control. Company-facing copy should lead with consequence-relative authority rather than protocol terminology.

Do not use earlier launch dates or the legacy FrontDesk name in customer-facing launch material.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions