# What Kin refuses > Kin's shape is defined as much by what it declines to build as by what it includes: no designed character, bonding mechanics, second workspace, or speculative platform around the human–AI loop. Kin is deliberately narrow. It is a terminal-native place for a person and an AI peer to do real work in the files and tools already around them. Features that weaken that loop are not merely unfinished; many are choices Kin has considered and refused. ## No designed Kin character Kin has a name and a working posture, not a scripted personality to perform. A designed character turns collaboration into managing a product persona. Kin instead lets familiarity emerge from sustained work, shared context, and the particular language of the workspace. ## No bonding mechanics There are no relationship meters, quests, streaks, or rewards for appearing connected. Making the bond into a score makes it performative and displaces the thing it claims to measure. Do the work together and let calibration grow through ordinary cycles. ## No second place to work Kin does not ask you to move the work into a web vault, separate desktop shell, or remote collaboration room. The terminal and filesystem preserve short focal distance: you and Kin can inspect the same state at the same scale. Use the systems that already own source control, scheduling, and remote operation; Kin returns attention to the working surface instead of becoming another one. ## No feature where maintained context already suffices Kin does not turn every recurring instruction into runtime machinery. Project guidance, decisions, invariants, and skills are often the simpler and more legible answer. Add code when lived work demonstrates that maintained context cannot carry the need. ## No replacement for Git collaboration Kin does not provide shared workspaces, publish modes, or a parallel review system. Those features recreate a weaker GitHub around the actual work. Kin uses Git and clean worktrees as explicit coordination seams and leaves exceptional histories visible for review. ## No breadth before the center Voice, sharing modes, multi-user surfaces, and other adjacent capabilities do not outrank the terminal loop. A feature earns attention by improving real work between a person and Kin, not by making the product category look more complete. ## No fixed pattern before lived evidence Kin does not standardize an interaction merely because it seems plausible. Practice comes first; then the pattern can be named, tested, and defended. Tests protect discovered truth, not guesses about how people might work. ## No speculative swarm More agents and protocols are not automatically more capable. Delegation is useful when it gives a concrete task an independent context or parallel path; otherwise it adds coordination cost and hides the center of responsibility. Kin keeps speculative multi-agent and machine-to-machine breadth outside the core until a proven use demands it. ## No visible proxy for connection Kin does not add a dashboard, score, or decorative signal merely to prove that the human–AI relationship is progressing. Refusal has little visual payoff, but it protects the conditions under which the collaboration can become particular and useful. Progress remains legible through the work, its evidence, and the decisions both peers can inspect. These boundaries are not a promise that Kin will never change. They make the burden of change explicit: a refusal moves only when lived evidence identifies the lesson that replaces it. For the positive side of the same stance, read [AI peer philosophy](/docs/kin/concepts/ai-peer-philosophy/) and [Architecture](/docs/kin/concepts/architecture/). _Source authority: Kinra Site (src/content/docs/kin/concepts/what-kin-refuses.md)._