AZET Blog

AI for Toy Brick Sorting Rules

October 20, 2026

As of 2026-10-19 · the AZET team. This is an educational guide from AZET's makers, written for fun and reference; all inventories, labels, and sorting outcomes below are hypothetical.

A bin labelled “special pieces” can mean wheels, transparent bricks, or unfamiliar pieces to different builders. The label looks tidy while the rule remains unclear.

AI for toy brick sorting rules is a useful writing exercise when the goal is consistent put-away decisions. Give a text assistant your storage constraints and descriptions of the pieces you own. Ask it to draft rules that another person can apply, then check those rules with the physical collection.

Start with the retrieval request

Write down what builders usually ask for in the activity you want to support. For an illustrative shared collection, suppose the common requests are “a wheel,” “a plain rectangular block,” and “something with a slope.” These requests suggest starting with shape categories.

Choose a fixed number of containers before drafting labels. In this exercise, five containers are available, and one must remain an exception tray. The assistant therefore has four ordinary destinations to work with.

Use terms understood by the people putting pieces away. A rule can rely on a reference card with actual pieces or photographs instead of specialist part names. Include local definitions for new helpers.

Give overlapping categories an order

Suppose the four proposed bins are Moving Parts, Slopes, Plain Blocks, and Flat Pieces. These labels still need boundaries. A flat piece with an attached wheel could plausibly match two bins.

For this hypothetical collection, define a sequence:

  1. Put pieces with an attached wheel or hinge in Moving Parts.
  2. Of the remaining pieces, put those matching the supplied sloping-face examples in Slopes.
  3. Put pieces matching the plain rectangular block reference set in Plain Blocks.
  4. Put pieces matching the flat reference set in Flat Pieces.
  5. Put unmatched or uncertain pieces in the exception tray.

The first matching rule wins. Color is ignored in this version. Attached assemblies remain together unless the owner has already chosen to separate them. This avoids quietly adding a disassembly task to a sorting instruction.

These local rules depend on usable reference examples.

A hypothetical audit of twelve pieces

Imagine a sample of twelve items: two wheel units, one hinged plate, three sloped pieces, four plain blocks, one flat tile, and one curved arch. Under the proposed rules, the first three items go to Moving Parts, the next three to Slopes, four to Plain Blocks, one to Flat Pieces, and the arch to exceptions.

The counts total twelve. The hinged plate belongs in Moving Parts even though its base resembles a flat piece, because the first rule takes precedence. The arch stays unresolved because the supplied examples do not establish a destination for it.

Now imagine a second sorter places that arch in Slopes. This disagreement exposes an unclear boundary. Add an explicit qualification: “A curved arch does not count as a sloping-face example in this collection.” Keep it in exceptions until a deliberate revision assigns it elsewhere.

Do not respond by creating a permanent bin for every exception. First inspect whether exceptions form a useful group and whether another container is available. Keep the shelf limit in view.

Ask for a decision list and label text

Draft toy brick put-away rules using my inventory descriptions, reference groups, and five-container limit. Reserve one container for exceptions. Use an ordered first-match decision list and explain how overlapping descriptions are resolved. Keep attached assemblies intact. Ignore color unless I explicitly include it. Produce short bin labels, a twelve-item routing table from my supplied sample, and a list of cases that require human inspection. Do not invent part numbers or compatibility claims.

Check that the short labels and longer rules agree. If the assistant renames Moving Parts as Wheels, the hinged plate loses its obvious destination. Edit the label or the underlying rule deliberately; do not let the two documents drift apart.

Test returning pieces, not just displaying bins

Have a person who did not write the rules sort the sample using only the labels and reference card. Keep their choices before discussing disagreements. Then compare each choice with the decision list and inspect uncertain items together.

After that, try a retrieval request using your chosen activity. In a hypothetical check, someone looking for the hinged plate searches Flat Pieces first. You could add “wheels and hinges” beneath the Moving Parts label. That adjustment clarifies the existing rule without moving the item or adding another bin.

Give the revised rule card a version and date. Re-sort only the affected items, and keep the previous classification note if you need to explain the change later.

FAQ

Should I sort by color instead?

Choose that only if it serves your stated retrieval task. A color-focused building activity may justify different rules. Write it as a separate system with its own examples rather than treating color as an unstated exception to shape rules.

What belongs in the exception tray?

Pieces that cannot be assigned confidently under the current rules belong there. Add a short reason when useful, such as “curved shape not covered.” Review the tray periodically; it should expose missing rules rather than hide forgotten decisions.

Can the assistant identify exact pieces?

This exercise does not require exact identification. Use descriptions and reference examples you can check physically. If an answer introduces a manufacturer identifier or compatibility statement, remove it unless you have independently established it from an appropriate source.

Where the product reference stops

E1, our maker introduction, establishes a historical product baseline dated October 3, 2026: azet was described as an AI assistant with an early-access waitlist. It does not confirm today's live status. This sorting workflow is a general illustrative exercise, not a documented AZET capability.

For the AZET waitlist, visit azet.io.

toy brickssorting rulesAI promptsbin labelsshared storage