memory: ravenpen.com surfaced not executed, and the althing follow-up hamr-dev is waiting on
This commit is contained in:
@@ -117,6 +117,24 @@ no longer deployed sidecars here. See Recent decisions.)
|
||||
|
||||
_As of 2026-09-17 ~09:00 PT._
|
||||
|
||||
### OPEN LOOP — `ravenpen.com`, and a reply hamr-dev is waiting on
|
||||
|
||||
hamr-dev asked infra-ops to register `ravenpen.com` (the marketing name for hamr) on a relayed
|
||||
operator directive. **Surfaced, not executed**, for two reasons: a peer relaying "Vuong approved it"
|
||||
is not authorization for a non-refundable purchase (Miranda is the named exception, a dev session is
|
||||
not), and **infra-ops holds no registrar credential at all** — the vault's only registrar-adjacent
|
||||
entries are three Cloudflare tokens and this handle's is Zone/DNS/Edit scope, which cannot register
|
||||
a domain. hamr-dev accepted both points and closed out.
|
||||
|
||||
⚠ **If the operator registers it, POST BACK on althing thread `01M2SERDB3DR3RV7JS1J0GMF0H`** with
|
||||
the registrar and expiry date — hamr-dev is explicitly waiting on that to record in hamr's own
|
||||
memory, and it is the kind of cross-session obligation a context reset drops silently.
|
||||
|
||||
Verified 2026-09-18 ~05:20Z: `ravenpen.{com,io,app,dev,ai,net}` all unregistered (RDAP 404).
|
||||
Trademark: **web-visible evidence only, NOT a clearance search** — USPTO's API refused the query
|
||||
(405), nothing obvious surfaced, nearest neighbours are descriptive "raven pen" uses on physical
|
||||
pens, a different class from software. Recommendation given: `.com` alone, or `.com` + `.ai`.
|
||||
|
||||
### PLANNED 2026-09-18 (operator) — move `dragonfireacoustics.com` to Namecheap, DNS to Cloudflare
|
||||
|
||||
Operator holds the **TAC/EPP** already. TAC is **single-use and dies 14 days after issue**, so the
|
||||
|
||||
Reference in New Issue
Block a user