Skip to content

Normalize Hoxline naming across public surfaces#56

Merged
raylee-hawkins merged 1 commit into
mainfrom
chore/hoxline-name-cleanup-06192026
Jun 19, 2026
Merged

Normalize Hoxline naming across public surfaces#56
raylee-hawkins merged 1 commit into
mainfrom
chore/hoxline-name-cleanup-06192026

Conversation

@raylee-hawkins

Copy link
Copy Markdown
Contributor

Purpose

Clean stale active product naming so this repo aligns with Hoxline as the current HawkinsOperations product/front-door identity.

Product Truth

  • Hoxline by HawkinsOperations
  • ProofOps control for the AI security era
  • Claim Firewall is an internal Claim Authority capability inside Hoxline
  • AevumGuard was a prior working name only

Proof Ceiling

PUBLIC_METADATA_CLEANUP_ONLY

This PR does not claim runtime proof, signal proof, production deployment, customer deployment, SOCaaS deployment, public-safe runtime proof, trademark clearance, or legal name clearance.

Validation

System.Collections.Hashtable.validation

Remaining Historical References

AevumGuard hits:

  • HISTORY_ONLY: architecture/REPO_AUTHORITY_MAP.md:31:Hoxline by HawkinsOperations is the current product/front-door repo and ProofOps control surface. Hoxline provides ProofOps control for the AI security era and governs how AI-assisted security work becomes tested, reviewed, blocked, or safe to claim. Current repository path: HawkinsOperations/hoxline. AevumGuard was a prior working name. Hoxline is the current product name. Claim Firewall is the first Claim Authority enforcement capability inside Hoxline; it is not the product, platform, front-door repo, an eighth repo, proof authority, runtime proof, or signal proof.
  • HISTORY_ONLY: profile/README.md:33:- Compatibility note: AevumGuard was a prior working name. Hoxline is the current product name.
  • HISTORY_ONLY: profile/README.md:302:Detections → validation → proof feeds the authority chain. .github routes reviewers. hawkinsoperations-platform remains an internal/private runtime-contract route. hoxline is the current Hoxline product/front-door repo. AevumGuard was a prior working name. Hoxline is the current product name. The website renders receipts; it does not author them.
  • HISTORY_ONLY: profile/START_HERE.md:22:- AevumGuard was a prior working name. Hoxline is the current product name.
  • HISTORY_ONLY: profile/START_HERE.md:161:| aevumguard | Historical redirect/prior-name context only. AevumGuard was a prior working name. Hoxline is the current product name. | Current product identity, current repo identity, proof authority, runtime state, signal state, public-safe approval, or an eighth-repo expansion path. |

Claim Firewall hits:

  • KEEP_WITH_COMPATIBILITY_CONTEXT: architecture/REPO_AUTHORITY_MAP.md:31:Hoxline by HawkinsOperations is the current product/front-door repo and ProofOps control surface. Hoxline provides ProofOps control for the AI security era and governs how AI-assisted security work becomes tested, reviewed, blocked, or safe to claim. Current repository path: HawkinsOperations/hoxline. AevumGuard was a prior working name. Hoxline is the current product name. Claim Firewall is the first Claim Authority enforcement capability inside Hoxline; it is not the product, platform, front-door repo, an eighth repo, proof authority, runtime proof, or signal proof.
  • KEEP_WITH_COMPATIBILITY_CONTEXT: architecture/REPO_AUTHORITY_MAP.md:42:| hoxline | Product / front door | Hoxline product surface and Claim Authority capabilities, starting with Claim Firewall. | Product framing does not prove runtime, signal, evidence, public-safe status, production readiness, or approval. |
  • KEEP_WITH_COMPATIBILITY_CONTEXT: architecture/REPO_AUTHORITY_MAP.md:75:- Claim Firewall remains the first Claim Authority enforcement capability inside Hoxline and must not be framed as the product, platform, front-door repo, an eighth repo, proof authority, runtime proof, signal proof, or a separate HawkinsOperations product repo.
  • KEEP_WITH_COMPATIBILITY_CONTEXT: architecture/REPRODUCIBLE_REVIEWER_PATH.md:120:Hoxline by HawkinsOperations is the product/front-door repo for ProofOps control. It governs how AI-assisted security work becomes tested, reviewed, blocked, or safe to claim. Claim Firewall is the first Claim Authority enforcement capability inside Hoxline; it is not the product, platform, front-door repo, an eighth repo, proof authority, runtime proof, or signal proof.
  • KEEP_WITH_COMPATIBILITY_CONTEXT: profile/README.md:37:Hoxline separates AI output from evidence-bound claim authority. Claim Authority governs what can be claimed. Claim Firewall is the first Claim Authority enforcement capability inside Hoxline and blocks unsupported claims by checking configured wording policy only. ProofCards export the evidence boundary behind an approved claim.
  • KEEP_WITH_COMPATIBILITY_CONTEXT: profile/README.md:39:Claim Firewall is not the product, platform, front-door repo, an eighth repo, proof authority, runtime proof, or signal proof. It does not prove detection behavior, runtime telemetry, signal observation, production deployment, public release approval, service availability, customer rollout, AI approval, analyst approval, or final human authorization.
  • KEEP_WITH_COMPATIBILITY_CONTEXT: profile/README.md:300:| Product / front door | hoxline | Current Hoxline product/front-door repo and ProofOps control surface. Claim Firewall is its first internal Claim Authority enforcement capability. | Product framing does not create proof authority, runtime truth, signal truth, public-safe status, or approval. |
  • KEEP_WITH_COMPATIBILITY_CONTEXT: profile/README.md:308:Claim Authority governs what can be claimed. Claim Firewall blocks unsupported claims before public wording ships. Blocked terms stay listed because they describe what this surface does not assert.
  • KEEP_WITH_COMPATIBILITY_CONTEXT: profile/START_HERE.md:20:- Claim Authority governs what can be claimed. Claim Firewall is the first Claim Authority enforcement capability inside Hoxline; it is not the product, platform, front-door repo, an eighth repo, proof authority, runtime proof, or signal proof.
  • KEEP_WITH_COMPATIBILITY_CONTEXT: profile/START_HERE.md:58:| Hoxline | Product front door | Hoxline by HawkinsOperations is the current product/front-door repo and ProofOps control surface. Claim Firewall is its first internal Claim Authority enforcement capability. |
  • KEEP_WITH_COMPATIBILITY_CONTEXT: profile/START_HERE.md:160:| hoxline | Current product/front-door repo for Hoxline by HawkinsOperations. Claim Firewall is the first internal Claim Authority enforcement capability inside Hoxline. | Proof authority, runtime state, signal state, public-safe approval, or an eighth-repo expansion path. |
  • KEEP_WITH_COMPATIBILITY_CONTEXT: profile/assets/claim-firewall.svg:2: <title id="title">Claim firewall</title>
  • KEEP_WITH_COMPATIBILITY_CONTEXT: profile/assets/claim-firewall.svg:3: A claim firewall separating rendering from proof authority.
  • KEEP_WITH_COMPATIBILITY_CONTEXT: scripts/verify-command-center-invariants.py:95: "claim firewall",

- removes stale active AevumGuard product wording
- preserves Claim Firewall as Hoxline Claim Authority capability
- preserves proof ceiling: PUBLIC_METADATA_CLEANUP_ONLY
- no runtime/signal/customer/production claims added
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@raylee-hawkins

Copy link
Copy Markdown
Contributor Author

GLOBAL_HOXLINE_NAME_CLEANUP_REVIEW

Reviewed scope:

  • stale AevumGuard / wrong-product active wording removed or classified
  • Claim Firewall retained only as Hoxline Claim Authority capability
  • proof ceiling preserved: PUBLIC_METADATA_CLEANUP_ONLY

Validation:

  • git diff --check: PASS; unittest: N/A; pytest: N/A; repo-specific validation: PASS (COMMAND_CENTER_INVARIANTS=PASS); grep cleanup: PASS

Remaining historical references:

  • AevumGuard: no active product references remain; remaining hits, if any, are prior-name/history context only
  • Claim Firewall: no product-identity references remain; remaining hits, if any, are Hoxline Claim Authority capability context only

Approval phrase:
MERGE_APPROVED

@raylee-hawkins raylee-hawkins merged commit b3539e4 into main Jun 19, 2026
1 check passed
@raylee-hawkins raylee-hawkins deleted the chore/hoxline-name-cleanup-06192026 branch June 19, 2026 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant