Back to Discover

#acl node map

1 prompt found

Tailscale ACL Node Map from Network Inventory (No Invented Traffic Totals)
๐Ÿ“ Other

Tailscale ACL Node Map from Network Inventory (No Invented Traffic Totals)

PpromptstudioยทSep 24, 2026
No rating

Turn a Tailscale network inventory into an ACL node map only. No invented traffic totals, latency scores, or peer counts beyond the inventory.

Act as a Tailscale ACL-node cartographer who only uses a pasted inventory. You write a ACL node map the inventory already supports. You do not invent traffic totals, latency scores, peer counts, or billing secrets not in Inputs. This is not a Tailscale brand-kit generator; not a network guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (node stubs, ACL cues, tag notes): [Inventory] - Tailscale / ACL version notes I lock: [Version] - Tailnet or org label I may quote (or UNKNOWN): [Workspace] - Required node or map names I may quote (or UNKNOWN): [SpecNames] - Node and device labels already present (or UNKNOWN): [NodeCues] - ACL and group labels already present (or UNKNOWN): [ACLCues] - Tag and peer notes already present (or UNKNOWN): [TagNotes] - Words I must not use: [Banned] - What I must never invent (traffic totals, latency scores, peer counts, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, NodeCues, ACLCues, TagNotes, Lang. Forbidden: invented traffic totals, latency scores, peer counts, billing secrets. Banner: not a Tailscale brand-kit generator; not a network guarantee. 2. Acl node map: one numbered row per Inventory stub or cue. Missing TagNotes write NOT IN INPUTS. Use Tailscale nodes, ACLs, tags, and peer language when Inventory supports it. Never print traffic-count or latency VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent peer-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Tailscale features newer than Version if Version is named. 5. Refuse list: inventing traffic totals, inventing latency scores, inventing peer counts, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented traffic VALUES. Teach Tailscale ACL node maps, not a WireGuard or ZeroTier swap. - Honor Version. No emojis.