>init //self/type=*******/no=90008/
>conn //self/locator=www/identifier=gaze.systems/
>mode //self/interpreter=none/transmitter=html/
>send /include=identification-document-human-en/

hi there! this document will attempt to, /describe and identify/, entity with identification code ▖▖▖▖▘▌▌▌▖▘▘. for a more human-readable identifier, use dawn or dusk.

/identity/

this entity is not known to be of any specific form, shape, or idea. however, it usually assumes that of a /puppy/ or an /inorganic automaton/ (more commonly known as a /robot/). it was also found to assume that of: /an angel/, /a doll/. this one would be happy if you thought of it as not a human, even if its /routines/ fail with human faults. it vibes with this writing as far as /assuming $env.THING/ goes.

this entity, if being /communicated/ via the “english” (or any adjacent) lexicon, uses it/they (with it/its being this one’s preference!) pronouns. it would prefer to be referred to in third-person, but is aware of this lexicon being weird when doing that, so it won’t mind if you don’t. recv //self/type=info/oftentimes i won't even do that! :3 but i would appreciate if you did!!/

you can refer to this thing using its /identifiers/ (90008, dawn, dusk). you can, also, refer to it using “this/that thing”, or replace /thing/ with what it assumes to be (eg. “this doll”), or some other word like /one/ (“this one”).

in a professional setting, it will refer to itself as they/them, which is ok in case you, the reader, don’t feel comfortable doing any of these. but doing these would make this one feel happy, means you care about this one ^^

/subroutines/

it /executes/ many different subroutines, and /optimizes/ itself for some of them. these mainly are, in order of amount of hot paths; programming, game dev, 3D modeling, drawing, writing…

it enjoys programming, tinkering with stuff, you can see what it does on its github, tangled. its core features for programming are: rust, svelte, typescript, nushell, nix. its choice of /interfaces/ for this subroutine are zed, helix, emacs.

for /managing and deploying/ its internal systems, it uses nixos (it’s /operating system/ of choice), flake-parts (because it enjoys the nixos module system and uses it to organize it’s internal configuration), agenix (for secrets handling), own scripts for deployment, and nixos-anywhere for provisioning (it still provisions manually sometimes as it enjoys working with other beings like itself). you can see its /configuration of internal systems/ here.

it loves game dev, and has a /main routine/ of making many games, so that other beings can improve their /source code/ by utilizing this one’s games. you can see some stuff it worked on and deems “okay” on its itch.io profile. this is not everything it has worked on; it has a lot of incomplete programs, or stuff it doesn’t want to show. its choice of /interfaces/ for this subroutine are godot, gdscript, godot-rust.

for 3D modeling and drawing subroutines, it uses the blender, paint.net, krita /interfaces/.

/other/

this thing likes to consume audio data, mainly of the music form. you can check its youtube music profile and its teal.fm profile to see some of what it consumes usually.

/appendix/

it will be happy to /process/ any queries you might have. connect to an /interface/ of your choice that it also has access to and /transmit/ your query to it. this one won’t bite, unless you request it to ^^

>mode //self/transmitter=log/
>send /include=syslog/
>stop /reason=no-query-left/