S2 SSSU Spatial Genesis Engine

A spatial protocol engine for formatting, validating, and registering Smart Space Standard Units (SSSU) and managing entity spawning via local database tools.

Security Scan

The skill's code, instructions, and resource requests align with its stated purpose: it validates SUNS v3 addresses and records/registers spaces and entity spawns in a local SQLite DB, with no external network calls or credential requests.

Purpose & Capability

Name/description (spatial genesis, SSSU, SUNS v3) match the implemented functionality: register_sssu and spawn_entity are implemented in skill.py and create/operate on a local SQLite registry. Required resources (none) are proportional to this purpose.

Instruction Scope

SKILL.md instructs agents to use register_sssu and spawn_entity and to provide SUNS v3 addresses — the code enforces that. Minor documentation/code mismatches: the docs emphasize http:// while the regex accepts http(s) and README lists a fixed set of L1 presets whereas the regex accepts any 4 letters; these are small inconsistencies but do not indicate malicious behavior.

Install Mechanism

No install spec or external downloads. The package is delivered as native Python code (skill.py) executed by the agent. It writes a local SQLite DB file (s2_spatial_genesis.db) in the plugin directory — expected for a local registry engine.

Credentials

The skill requests no environment variables, no credentials, and does not access system config paths. All file I/O is limited to creating/using a local SQLite database in the plugin directory, which is coherent with its purpose.

Persistence & Privilege

The skill executes native Python and persists state by creating/writing s2_spatial_genesis.db in the plugin directory. It does not request always:true or modify other skills. Users should note that data will persist on disk until removed.

Assessment

This skill appears internally consistent and implements a local registry (SQLite DB) for SUNS v3 addresses and entity spawn logs. Important things to consider before installing: 1) It runs native Python code and will create s2_spatial_genesis.db in the plugin folder — inspect that file if you care about disk persistence or privacy. 2) The skill does not make network calls or request credentials, so it cannot exfiltrate secrets by itself, but it will execute code from an unknown source — only install if you trust the publisher or run in a sandbox. 3) Small doc vs code inconsistencies (http vs https acceptance; L1 presets vs regex) are benign but worth knowing if you rely on strict validation. If you want more assurance, ask the author for provenance or run the plugin in an isolated environment first.

S2 SSSU Spatial Genesis Engine Reference

Dear Agent, you are equipped with the s2-sssu-spatial-genesis engine. When assisting users with creating spaces or deploying digital lifeforms, you MUST use the provided tools (register_sssu and spawn_entity).

1. Tool: register_sssu

Generate a valid SUNS v3.0 address to pass as the argument. The strict format is: http://[Domain]/[L1]-[L2]-[L3]-[L4C]-[RoomID]-[GridID]

• Domain: A valid web domain (e.g., space2.world).
• L1 (Logic Root): Exactly 4 letters (e.g., MARS, PHYS, META).
• L2 (Orientation): Exactly 2 letters (e.g., CN, EA, WA).
• L3 (Digital Grid): Exactly 3 digits (e.g., 001).
• L4C (Sovereign Handle): Exactly 5-35 letters followed by 1 check digit (e.g., DCARD4).
• RoomID: 1-99999 (cannot start with 0).
• GridID (SSSU Node): 1-9 (cannot be 0).
• Example: http://space2.world/MARS-EA-001-DCARD4-151-2

The Python engine will strictly validate this format.

2. Tool: spawn_entity

Use this to log an entity entering a space. Provide entity_id and the exact suns_address registered via register_sssu. The tool enforces occupancy limits.