Organization and links

Learn to find the same record by period, relationships, projects, resources and topics. Distinguish links for reading between documents from memberships for collecting records by group.

Five browsing axes

• Period: Browse using verified dates, times and intervals in records.
• Relationships: Collect records connected explicitly to people and organizations.
• Projects: Collect events, schedules and wikis assigned to the same project.
• Resources: Group by materials, tools and systems you reference or use. This does not mean attachment file types.
• Topics: Classify by work areas or interests such as customer support, authentication or product planning.

The 3 in 3×5 means past, present and future views; 5 means the axes above. The present range extends 15 days before and after the reference date in the archive time zone. “Present” is not a status that automatically groups all work in progress.

Prepare canonical group documents

Canonical pages for people, organizations, projects, resources and topics are typed wikis or reference documents. Search for an existing target before creating another document with the same name.

1. Search the wiki list by title or alias for an existing target.
2. If none exists, create a canonical page with New record › Create wiki.
3. Under Organization and links › Target type, select person, organization, project, resource or topic.
4. Enter a description that identifies the target, not just a name, and useful aliases, then save.

This prepares a reference page for collecting records. Saving a new canonical document does not automatically assign existing records to that group.

Connect records to a group

1. Open and edit the diary, wiki or schedule you want to classify. In wikis, expand Organization and links.
2. Choose the Relationship type under Classifications/relationships. People and organizations use relationships; projects, resources and topics use their corresponding axes.
3. Under Find target by name, choose the actual canonical document in the same archive. If titles match, read descriptions to select the right target.
4. Enter a Participation role for a person or organization if needed.
5. Select Add relationship, then Save the record. Selecting a target alone, or adding a relationship and cancelling record saving, does not persist the result.

Add each axis separately to connect several. To change an existing relationship, select it in the list, apply Change relationship, and save the record.

Period is not an additional group chosen from this relationship type. Enter verified record dates, times or intervals and choose year/month/week and range in period browsing. Do not invent a date if it is unknown.

Body links versus membership

A body link means “also see this”; group membership means “this record relates to this target.”

For example, writing “Website redesign” in meeting minutes or linking to its project wiki does not automatically count those minutes as project members. Add the project under Classifications/relationships to collect them there.

Select an actual target under Internal links in the wiki editor to insert a body link. Keep evidentiary originals as source/evidence links. A current navigation target and a pinned source revision serve different purposes.

Confirm connections and counts

1. Save the record and open the target in the chosen relationships, projects, resources or topics.
2. Confirm the linked record appears. Check whether search, period or diary/wiki filters hide it.
3. Compare period records with entered event/scheduled dates and the archive time zone.
4. Separately confirm that body links open the correct target.

Copying documents into an archive does not populate classification, relationship or schedule counts. If counting finishes but there are no connected records, check that real memberships, dates, plans and schedules were saved before importing materials again. Do not interpret loading or failed empty counts as zero.

One record can appear on several axes, so adding their counts need not equal the total number of records. Document counts, dated event/schedule counts and directly linked group counts are different values.

Partial loading and retry — source contract, 2026-11-05

Counts, individual classification axes, events/schedules, recent updates and goals load separately. Failure in one area preserves other loaded areas and document browsing. An uncounted indicator such as — means not known yet; a real 0 means zero under the current conditions. Retry reloads only the failed area; Load more continues only its classification.

If archive data changes during a query, it reloads once to avoid mixing counts from different revisions. Continuous changes show a retry notice. Temporarily missing numbers do not mean data deletion. This describes the source behavior contract, not installation, production deployment or completed verification.

Cautions

Classification does not create facts absent from records. Do not guess people, projects or dates; leave them for confirmation. When asking AI to classify, distinguish proposals from actual saved results.

Group links do not grant archive access. See account and permission guidance for organization invitations, roles and archive AI access settings.

A resource is a conceptual reference target; a file is actual bytes. Even while file features are suspended, do not remove existing file sources or links or replace them with arbitrary text documents.