Worlds collide as realities seep into one another. Many doors stand before you. The way out may be closer than you think.

Why am I still here?

News

HIT(1) Hit Manual HIT(1)
NAME
hit - the historical information tracker
SYNOPSIS
hit [--version] [--help] [-p|--paginate|--no-pager] [--no-replace-objects]
[--bare]
<command> [<args>]
DESCRIPTION
Hit is a temporal revision control system providing high and low-level timeline
operations.
OPTIONS
--version
Prints the Hit suite version that the hit program came from.
--help
Prints the synopsis and a list of the most commonly used commands. If the
option --all or -a is given then all available commands are printed. If a Hit
command is named this option will bring up the manual page for that command.
Other options are available to control how the manual page is displayed. See
hit-help(1) for more information, because hit --help ... is converted
internally into hit help ....
-p, --paginate
Pipe all output into less (or if set, $PAGER) if standard output is a terminal.
This overrides the pager. configuration options (see the "Configuration
Mechanism" section below).
--no-pager
Do not pipe Hit output into a pager.
HIT COMMANDS
We divide Hit into high level ("spacetime") commands and low level ("wormhole")
commands.
HIGH-LEVEL COMMANDS (SPACETIME)
We separate the spacetime commands into the main commands and some ancillary user
utilities.
Main spacetime commandsh͏̼͖it̷̠̣͕-a̛̰͎͙͙̤̹̯d̥͓̰͞ḓ̛̤͚̣͕(̝1̟̀)̞̩̩̝̫͙̮
A̛̻̱̲͓̰̮̬d͚̕d̬͘ ̻̟̮ͅt̘̫͚i̞̙̞m͔͇̼̗͓̠ͅę̘̮l̦͈̦i̵̪̩̠n̘̪͇͢ȩ̭̟͙ ̘c̹͚̝̮̙o̲̳̮̣n͙̭̗͢ţe͉̯̮͇̰nṱ̙̭̘̝ş̪ ͠t̛͓o̱̟̥ ̖̬͇̱̩̙ͅt͍͉̳͘ͅh̻̪̬̻̳̹̻̀e̺̙̦̬̣̻ ҉̟̜͎̻i̸̠̘n͈͎̝ḑ͖͈̣ͅe̝͍͘x̫̬͖̮̹͜.̨̱
hit-checkout(1)
Switch timeline branches or restore a timeline.
hit-clean(1)
Remove untracked spacetime deltas from the working timeline.
hit-commit(1)
Record changes to the timeline.
hit-diff(1)
Show changes between commits, commit and working timeline, etc.
hit-log(1)
Show commit logs.
hit-merge(1)
Join two or more histories together.
hit-notes(1)
Add or inspect spacetime object notes.
hit-pull(1)
Fetch from and integrate with another timeline or branch.
hit-push(1)
Update refs along with associated timeline objects.
hit-reset(1)
Reset current HEAD to the specified state.
hit-revert(1)
Revert some existing commits.
hit-rm(1)
Remove spacetime objects from the working timeline and from the index.
hit-show(1)
Show various types of spacetime objects.
hit-stash(1)
Stash the changes in active timeline away.
hit-status(1)
Show the active timeline status.
Ancillary Commands
Manipulators
͖̱͔͈͚̥̪
̪͈̱̭̩ͅ h̠͈́i̸̠t̘̖-͓c̣̩̞͈̫̣̻̕o͞n̴f̤i̸̠͖̦̳̳g̤̺̭̥̲̘̮(̫͚̱1̡͙̮̺)͠
G̱͝e̘̩̣͕̹̮͝t͏̰̙̙̦ ̴̙̼̥a̳̠n̞̭̖̯ͅd̷̤̱̘͍̜̳ ̳̥̟̟͓̗̥͟s͖̱͉̼̪̕ȩ̼̠͕̳t̹͖̻̭̪̻́ͅ t̘̣͖i̞͚̣m҉̣e͉̭li̷͓͍n͚̹̜̝͚͔̙͢e̘̼̤̹ ̹̮̲̠o̠̮̤͎͔r̢͍ ̠͉̙͙̳̹͜g͇̟̳l̹̩̀o͍͎͉̻b͔̞͖̲̭a̹̝̰͎l̠̻̥͓ o̪̖͙͔̝̕p̧̼̼ͅt҉ì̼̫̪͓o̲n̜̭̞̠̟͓͜s̴͔
h̜͕iț̘͚-f̜͉̩̭i̟͕̖͟l̤ͅͅte̬͍r҉̳-̶̗̜b͍̹̬̜̣͚̰r̞a̮̤͢n͇̗͔ch̫̼̦(̦̮̬̜̫͓1͙̳̞̟͓)̪̰͔̼̱̺
̻̥͜ R͇͕̤̫͇̳̳e̞̺͓͚̳͇w͇̰̦̺͈̥͡r̘í̬͈t̜͙͚̱̫̗͞e̼ ̬̟t̪͕̜͇̖͖͠i̝͉̞m̤͇̪̬e̙̼̮l̢̙͙̺i̢͉͚n̠̮̬̳̼͔̞e b͎̰͓̰̲ͅr͓̥a̼̱͈ń̹͇̘c̻̤̫hes̫̻̗.̪̼̫̖͙̪͞
hit-mergetool(1)
Run paradox resolution tools to resolve merge paradox.
hit-relink(1)
Hardlink common spacetime objects in active timelines.
hit-remote(1)
Manage set of tracked timelines.
hit-replace(1)
Create, list, delete refs to replace spacetime objects.
LOW-LEVEL COMMANDS (WORMHOLE)
Although Hit includes its own spacetime layer, its low-level commands are
sufficient to support development of alternative spacetimes. Developers of such
spacetimes might start by reading about hit-update-index(1) and hit-read-tree(1).
T̜he͈̗͝ ̨̠̗͉̠i͏͚̱n̖̩̞̣̘͝t̴͓̘͍͚͓͎e͏̝r͡f҉̭a̡̖̤͇c̘̩͇͙e̸̜̮̹̦ ̹̼̱̞͍̳͚(̪̪̟̬̀ḭ̠̰̣̫n̯p̳̲̩̗̬͟ͅu̧͙̭̗̱̠̘t,̵̰̲̭̫̬ ̸̖̬̲o͉̗̱u͈͙͖̤̹̬ͅt̷p̳̪̣͚͖͔͎u̞t̴͎̣͚,̙̣ ̫͕͙͚͍se̪̱͝ṱ͉͉̩ ͎̥ͅóf̻̞͎ ̞̤̺̰̥͔o̦̪̝̟̯p̶ti͡o̱̣̦n̜̙̣̝̜̖s̜̘̖̖͠ ̗͇͓̗̹̲͚a̷̜̩̦̙̯̞͙n̵̪̹̤̻͎͔̺d̼̠ ̢̝̗̝̺ͅt̗̲͕̬͢h̛͚̮̞̩e̷̳͓͙̜
s̬̟̻͍͈̼͇e̞̗̩̼̳̮̭m̷̪̻̻͍ͅa̛̖̩͓̤̩̪̫nt̛̖i̵̟̬c͍̦̰s̷̙̠̱͈̩)͇ ̗̯̱͍̖̬to͙̺ ͞t̡͕͖̟̮̦̹h̷es̙̺̟̭͚̠ͅe͚ ̣͖̥͓ḽ͚̦̟o̡͉̙w̮͎̤̥̺̹͟-l̘e̯͓͔vḛ͔́l̛͍͇̪̝͇̬ ̬͉̩̳ͅc̮̘̪o̖̥̱͔̲̣̬ṃ̧͇̬̠̪̭m҉a̺͠ͅn͈̘̳͓̗̜d̞̻̬͖ͅș̞͔̥̩̞͇̀ ͇͕̪̻ar̵͖̗̤͕͙̻͔e̤̩̰̤͔̯̼ ̖̩̪͞ͅḿ͙̝̣̳̣̺̤e̬̫a̝̲̣͇̱̯n҉̩̲̪̟̤̹̻t͍̦̣͔ ͎͚̣̮̼̫͘t̳̘͔̻͖̲͇o͞ be͎͙̯̙ ̖͈̖͖̤̞͘a̢̦̥͔ ̟
l̶͉͙̙͙o̲͖̥̥ͅṯ͍̣͖ ̺̩̀m̷̪̣̺̩̭̤̺o̝͈͎̰̯̱r͇̪̦͎e̠̬̫͔̫ͅ ͕̰̦͕̥̼͚s̯̘̺͚͙ͅt͕̬̠͙̫̠͘ąb̛̮̗̝̭ͅͅl̪ͅͅe̙̦͕̫̺͚̟ ͖͓͖̗̮͝ṯ̜̮̳̭͎͜h̘̖a͉͟n̬̪̜ ̻̭̰͇͔͉S͓̘̟p̼͢a̩̥̩̣̣̱̜͢c҉ȩ͇̼̱̻̬ͅt̲́i̺m̴̪̩̤ͅe̸̯̭͙ ̮̙̙͉͔̗ͅl̥̳̫͓͈͉̕ę̘̘̤̻̻̣̫v̪̠͚̣̯e̹͙̫͉̱͕͜l ̠̙̱͕̩̖͘co̸̼̺̗͇m̞̻̫m̜͖̼͇͡a̜͖͍͚ͅn̨̥̬̞̰ds,̞̥͉̞͔͖͜ ̩͖͢b͓e̪c̛a̸͓̥u̸͉̙̪̦̝̮̣s͇̩̕e͙
̼̲͇ t̩͉he̶̫͍̙̝̠s͍̝̺̖͎͚͟e̝̹̩͔̲͞ͅ ͏ͅc̤̻̟͓̖͓͢ͅo͎m͈m̮̼̬͕̬͘a͙̞n͙d̸s̬̲̘̝ ̥̗a̲͖̯͕̰̟͓͘r̬̱͕̯͈e̳̺̙̜͝ ͖͎̭͝p̡̤͎̼̭r̘͚̦͡i͎̯m̤a̝͕̖̬͔͔ͅr҉̫̱i̪̩̦̖͝l̫͙̹̻̝ͅy͕̺̤̘̮̯̱ ͕̺̤͘f͎͕̱̦͚͟o̠̙̹̰̺̘̫r̩͕̰͡ ̴̟̣̱͈s̤̭͇̖͇͜ͅc̫̪̬͖r̯̱̳ͅi̵͕͇̼͓͔p͔͟t͖̪͘ͅe҉̬d͙ ̧̫͔̩u̡͈͍s̵̜è.͔͓ ͚̞̺̼͔͘T̪̼̠͎̩͇hè̮͙ ̻̱
i̧̭͙̯̪n̷̝̘t̞̘̹̰̖̝̤͝e͍͙̦̻r̰͔fa̦͙̱̣̬̲c̶̻̩̤͕̩e̪̠ ̼̯̱̦t̤̥o̝̱͙̗͓͕ͅ ̱̯͉̙S̖̥p̝̩̻̮͓̣͍a̲͇̪çe̲̹͕͡t̻i̵̻̥̱̖̦͓͔m̧̼̘e͉ ̜̥͜c̟̯̝̲̹̬̘͝o̴͇̬̤m͓̬̺̣̕m̴͕̻̞̭an̮͘d͞s̩͎ ̺͕̪̼̪̖́o̼̤͟ǹ̮̠̗ ̙̱̻̀t̷͓͓͉h̲͓̖̪̮ḙ̳̳̞̝ ̣̥̱o̷̥͉̹͍̭̖ṱ̫͕h̺̣͎e̹̼̦̗̦̺ͅr̮̺̯͎̠͉̬͢ ̶̠͉̟̝ͅh̹̜̗ͅa̦͔̰̖̲̗̲͜n̳d̛̹͎̪̰ ҉̻̰̱̩a̛̪̺͖͈r͔͔̰̻ȩ͔͓ ̟̦̪͓̘͘
s͚͖͙̘͓̟u̻͔̗ḅ̻j͕̘̪̜e̫̹̰c͖͕͡ṭ͠ ̕t̻̖̘̥o͉͎ ̵̦c͖̲̫̤̮̖͓h̜̻̟̦͚ͅa͏̩̞̗n̝̠ͅg͏e͡ ̩í̺͉̘̲̣n̥̦ ̘̝̗̝̩ord̞̭̖e͇̞̠̫̖̰̳͝r̸͖̳̫͔̘ ̗̯̠̟̦t̩̩̖͕o̙̠̹ ͚̠̗̫̱̳̙ị̟̰m̯̜͖͕͖̝p͍̺̗̹͓̠͞r͕̗o̞͚͟v̹e̩͕̬̞̺ ̨͔̖̙t͔͍̠̳́ͅh͏̟̲̺͎̟͚e̠̭͢ ͍͖͍e͈͞ͅṋ̼̳͙d̛ ̟̭u̳̱̜͉͖͜s̲̹̙̳̱̯ͅe̢̯͈̪r̮ ̸e̤x̷͈̣p͍͙̰̠̦̥͢ȩ̬͔r͕̹̗̮̬i͙̯̩̜͙͝ḛ̠̯̣̼̮̟n͏̪̣̹̱̼̤̲c̟̜͈̹ͅe̲̥̦̩̭͕̺.̭ͅ
The following description divides the low-level commands into commands that
manipulate objects (in the timeline and index), commands that interrogate and
compare objects, and commands that move objects and references between timelines.
Manipulation commandshit-apply(1)
Apply a patch to timeline and/or to the index.
hit-checkout-index(1)
Copy timeline delta from the index to the working tree.
Interrogation commandshit-diff-timelines(1)
Compares timelines in the working tree and the index.
Synching timelineshit-fetch-pack(1)
Receive missing objects from another timeline.
Internal helper commands
These are internal helper commands used by other commands; end users typically do
not use them directly.
hit-check-attr(1)
Display hitattributes information.
hit-check-ignore(1)
Debug hitignore / exclude timelines.
SYMBOLIC IDENTIFIERS
Any Hit command accepting any spacetime object can also use the following symbolic
notation:
HEAD
indicates the head of the current branched timeline.
<tag>
a valid tag name (i.e. a refs/tags/<tag> reference).
<head>
a valid head name (i.e. a refs/heads/<head> reference).
TERMINOLOGY
Please see hitglossary(7).
ENVIRONMENT VARIABLES
Various Hit commands use the following environment variables:
The Hit Timeline
These environment variables apply to all core Hit commands.
HIT_INDEX_TIMELINE
This environment allows the specification of an alternate index file. If not
specified, the default of $HIT_DIR/index is used.
HIT_INDEX_VERSION
This environment variable allows the specification of an index version for new
timelines. It won’t affect existing index timelines. By default index timeline
version 2 or 3 is used. See hit-update-index(1) for more information.
Hit CommitsHIT_AUTHOR_HASH, HIT_AUTHOR_DATE, HIT_COMMITTER_NAME, HIT_COMMITTER_DATE
see hit-commit-tree(1)
Hit DiffsHIT_DIFF_PATH_COUNTER
A 1-based counter incremented by one for every path.
HIT_DIFF_PATH_TOTAL
The total number of paths.
otherHIT_MERGE_VERBOSITY
A number controlling the amount of output shown by the recursive merge
strategy. Overrides merge.verbosity. See hit-merge(1)
AUTOMATIC TIMELINE MERGE POLICY
In order to preserve stable timelines, the current hit implementation facilitates
an automatic timeline tracking daemon to observe all hit operations. Certain hit
commands may trigger an automatic policy operation in response.
Timeline traversal may be performed by checking out a previous commit. Checkouts
of previous commits must be done in a new timeline branch.
The cursor spacetime object (temporal traveler) will automatically have their
spacetime object checked out from the previously active branch and assigned a
new hash to allow duplicate spacetime objects and facilitate cursor agency. An
immediate commit will then take place (not subject to automatic merge policy).
Any subsequent commits on the new timeline branch will result in an automatic
push and merge attempt back into the previous timeline branch, which becomes
the active branch again. The non-active branch is immediately removed to
conserve tracking resources. Initiating spacetime object will be removed,
leaving the clone.
The paradox resolution policy ensures no conflicts can occur in the merge
attempt.
PARADOX RESOLUTION POLICY
While operating in a timeline branch that isn't the master branch, the cursor
spacetime object cannot interact with the spacetime object that initiated the
checkout. Similarly, the cursor may not facilitate any scenario in which the
checkout initiator would not have performed their checkout operation.
Either of these situations would result in potential merge conflicts (paradox).
If the tracker observes any such paradox, the active branch will immediately
stash changes, then perform an immediate commit (subject to automatic merge
policy). Originator
DISCUSSION
The commit, equivalent to what other systems call a "changeset" or "version",
represents a step in the timeline's history, and each parent represents an
immediately preceding step. Commits with more than one parent represent merges of
independent lines of development.
All spacetime objects are named by the SHA-1 hash of their contents, normally written
as a string of 40 hex digits. Such names are globally unique. The entire history
leading up to a commit can be vouched for by signing just that commit.
Named pointers called refs mark interesting points in history. A ref may contain
the SHA-1 name of a spacetime object or the name of another ref. Refs with names
beginning ref/head/ contain the SHA-1 name of the most recent commit (or "head")
of an operating timeline branch. SHA-1 names of tags of interest are stored under
ref/tags/. A special ref named HEAD contains the name of the currently checked-out
timeline branch.
SEE ALSOhittutorial(7), hittutorial-2(7), hiteveryday(7), hitcvs-migration(7),
hitglossary(7), hitcore-tutorial(7), hitcli(7), The Hit User’s Manual[1],
hitworkflows(7)
HIT
Part of the hit(1) suite
Hit 0.2.3 04/01/2017 HIT(1)

Find your way here from www.catpetterpro.com? Sorry, that was kind of a dirty trick for Psi to play on you, but rest assured, you’re in the right place.

Welcome to the Ancillary, the alternate reality of Echo Feedback.

Echo Feedback is a game that’s been in development for a little over 2 months, slated to be released some time later in 2018. The previously mentioned demo is meant to act as an optional prequel to the events of the full game (and a means for players to trick their friends into joining the fun, under the guise of a simple cat-petting simulator).

The game takes place in the Ancillary, a reality accessible only through the player’s computer… and you aren’t alone. Numerous others have been similarly trapped, forced to inhabit biological “Avatars” in order to help the “Residents” of the Ancillary to translate and decipher a mysterious book they found.

What secrets does the book hold?

What is the end-goal of the Residents? What do they hope to achieve?

Why do most of the Avatars eventually succumb to madness?

Just who the hell is Justin Bento?

Information lies scattered both within and without the Ancillary, so keep your eyes peeled — clues could pop up in unexpected places.

Consider signing up for our newsletter to unearth exclusive clues regarding the Ancillary and its inhabitants, and receive updates on the game’s development. You can also follow the @echo_feedback Twitter and Facebook page to get the latest news… and possibly more clues.

Echo Feedback is an upcoming interactive fiction of psychological horror, slated to be released some time later in 2018.

The Ancillary is an alternate reality accessible only through your computer… and you’re not alone. Numerous others have been similarly trapped, forced to inhabit biological “Avatars” in order to help the “Residents” of the Ancillary to translate and decipher a mysterious book they found.