From: Thomas Walker Lynch Date: Mon, 29 Jun 2026 10:45:51 +0000 (+0000) Subject: updating documents for RT-Style v4 X-Git-Url: https://git.reasoningtechnology.com/RT-Manuscript_locator.js?a=commitdiff_plain;h=7130f7785cdcb749d4c0042bdf35194c65f0a482;p=Harmony updating documents for RT-Style v4 --- diff --git a/administrator/document/RT-Manuscript_locator.js b/administrator/document/RT-Manuscript_locator.js new file mode 100644 index 0000000..704752b --- /dev/null +++ b/administrator/document/RT-Manuscript_locator.js @@ -0,0 +1,51 @@ +/* + indirect.js + + We have four scenarios + + immediate - used in the RT-Style distribution itself (authored, consumer, staged) + direct - used in the RT-Style project itself, but not in the distribution + indirect - the version all Harmony projects use + URL-only - always pulls style through a URL, a webserver must be present + +*/ + +window.RT = window.RT || {}; + +// --- Configuration --- +// Define the consumer project name to allow dynamic local file:// calculation. +window.RT.project_name = "Harmony"; + +// Fallback URL when served over a network where the project root is not in the URI. +window.RT.server_url = "http://localhost:8000/shared/linked-project/RT-Style/Manuscript"; + +(function() { + let style_path = window.RT.server_url; + + if (window.RT.project_name) { + const path = window.location.pathname; + const project_root_index = path.indexOf('/' + window.RT.project_name + '/'); + + if (project_root_index !== -1) { + // substring(0, stop) extracts up to the project name, leaving off the trailing slash. + // We append the explicit forward slash before navigating into the shared boundary. + const absolute_project_root = path.substring(0, project_root_index + window.RT.project_name.length + 1); + + // The symlink 'RT-Style' already drops us inside the 'consumer/' directory, + // so we proceed directly to 'Manuscript'. + style_path = absolute_project_root + "/shared/linked-project/RT-Style/Manuscript"; + } else { + console.warn("RT-Style: Cannot locate project root '/" + window.RT.project_name + "/' in URI. Falling back to server_url."); + } + } + + window.RT.dirpr_library = style_path; + + document.write( + ' + - + +

" in line.lower(): @@ -47,7 +47,7 @@ def deploy_RT_Style_indirect_locators(locator_dir_path): print(f"Warning: Could not read {file_path}: {e}") if needs_locator: - target_file = current_path / "RT-Style_locator.js" + target_file = current_path / "RT-Manuscript_locator.js" # Eliminate permission denial on read-only artifacts if target_file.exists(): @@ -60,7 +60,7 @@ def deploy_RT_Style_indirect_locators(locator_dir_path): if __name__ == "__main__": if len(sys.argv) != 2: - print("Usage: python3 deploy_RT_Style_indirect_locators.py ") + print("Usage: python3 deploy_RT_Manuscript_indirect_locators.py ") sys.exit(1) - deploy_RT_Style_indirect_locators(sys.argv[1]) + deploy_RT_Manuscript_indirect_locators(sys.argv[1]) diff --git a/developer/document/RT-Manuscript_locator.js b/developer/document/RT-Manuscript_locator.js new file mode 100644 index 0000000..704752b --- /dev/null +++ b/developer/document/RT-Manuscript_locator.js @@ -0,0 +1,51 @@ +/* + indirect.js + + We have four scenarios + + immediate - used in the RT-Style distribution itself (authored, consumer, staged) + direct - used in the RT-Style project itself, but not in the distribution + indirect - the version all Harmony projects use + URL-only - always pulls style through a URL, a webserver must be present + +*/ + +window.RT = window.RT || {}; + +// --- Configuration --- +// Define the consumer project name to allow dynamic local file:// calculation. +window.RT.project_name = "Harmony"; + +// Fallback URL when served over a network where the project root is not in the URI. +window.RT.server_url = "http://localhost:8000/shared/linked-project/RT-Style/Manuscript"; + +(function() { + let style_path = window.RT.server_url; + + if (window.RT.project_name) { + const path = window.location.pathname; + const project_root_index = path.indexOf('/' + window.RT.project_name + '/'); + + if (project_root_index !== -1) { + // substring(0, stop) extracts up to the project name, leaving off the trailing slash. + // We append the explicit forward slash before navigating into the shared boundary. + const absolute_project_root = path.substring(0, project_root_index + window.RT.project_name.length + 1); + + // The symlink 'RT-Style' already drops us inside the 'consumer/' directory, + // so we proceed directly to 'Manuscript'. + style_path = absolute_project_root + "/shared/linked-project/RT-Style/Manuscript"; + } else { + console.warn("RT-Style: Cannot locate project root '/" + window.RT.project_name + "/' in URI. Falling back to server_url."); + } + } + + window.RT.dirpr_library = style_path; + + document.write( + ' + - - + + - + - +

Program file system objects

@@ -30,11 +36,11 @@

- If a file represents a module or name space, follow the same naming conventions specified for classes and name spaces in the format_RT-code.html document. + If a file represents a module or name space, follow the same naming conventions specified for classes and name spaces in the format_RTÂ·code.html document.

- Other program files follow the same naming conventions specified in the format_RT-code.html document for an identifier of the + Other program files follow the same naming conventions specified in the format_RTÂ·code.html document for an identifier of the contained or related language.

@@ -58,9 +64,9 @@

Who uses each file with this property. Home directories are named like this.
The role of the people using the file. The developer and tester directories were named in this manner.
The role of the people using the file. The developer and tester directories were named in this manner.
What program are the files for.
The generic category of program said files are for. We prefer the names authored and made. authored files are those written by humans or AI, while made files are products of tools.
The generic category of program said files are for. We prefer the names authored and made. authored files are those written by humans or AI, while made files are products of tools.

Property indicators on files

@@ -68,9 +74,9 @@ We add a second property to a file using dot extensions to the file's name. We can extend the dot suffix model by using multiple dot suffixes. File name extensions are used to signal to the build tools how the file is to be processed:

.cli.c : Compiler fodder made into a stand-alone executable.
.lib.c : Library code source, compiled as an object file and added to the project archive.
.mod.c : Kernel module sources.
.cli.c : Compiler fodder made into a stand-alone executable.
.lib.c : Library code source, compiled as an object file and added to the project archive.
.mod.c : Kernel module sources.

Exercises

@@ -79,11 +85,11 @@ Rename the following poorly named files to strictly adhere to the RT naming conventions. Pay close attention to the language culture, the capitalization of acronyms, and the rule for spelling out abbreviations in outer scope identifiers.

A C-culture makefile that builds a target library and command line interface: target-lib-cli.mk
A Lisp-culture source file for an HTML parsing module: html_parser_mod.el
A C language source file that initializes an HTTP server: init-http-srv.c
A C-culture makefile that builds a target library and command line interface: target-lib-cli.mk
A Lisp-culture source file for an HTML parsing module: html_parser_mod.el
A C language source file that initializes an HTTP server: init-http-srv.c

- +

diff --git a/developer/document/single-file_C-module-and-namespace.html b/developer/document/single-file_C-module-and-namespace.html index 61acebe..1782008 100644 --- a/developer/document/single-file_C-module-and-namespace.html +++ b/developer/document/single-file_C-module-and-namespace.html @@ -1,44 +1,50 @@ + + C modules, namespaces, and the build lifecycle - + - - + + - + - +

Single-file C source

- The RT C language culture abandons the traditional separation of declarations into .h header files and definitions into .c source files. A developer integrates the interface and the implementation into a single file. + The RT C language culture abandons the traditional separation of declarations into .h header files and definitions into .c source files. A developer integrates the interface and the implementation into a single file.

- When a person includes the file using an #include directive, the file exposes only its interface. When the build system compiles the file into an object, a preprocessor macro acts as an implementation gate to compile the definitions. This keeps the source tree clean and ensures the interface and implementation never fall out of synchronization. + When a person includes the file using an #include directive, the file exposes only its interface. When the build system compiles the file into an object, a preprocessor macro acts as an implementation gate to compile the definitions. This keeps the source tree clean and ensures the interface and implementation never fall out of synchronization.

Ad hoc namespaces

- The C language lacks native namespaces. To prevent symbol collisions in large projects, RT code format uses a center dot (Â·) to denote ad hoc namespaces within identifiers. + The C language lacks native namespaces. To prevent symbol collisions in large projects, RT code format uses a center dot (Â·) to denote ad hoc namespaces within identifiers.

- A programmer maps the directory structure directly to these namespaces. For example, a file located at authored/ExampleGreet/Math.lib.c belongs to the ExampleGreet namespace and defines the Math module. + A programmer maps the directory structure directly to these namespaces. For example, a file located at authored/ExampleGreet/Math.lib.c belongs to the ExampleGreet namespace and defines the Math module.

Types and modules use PascalCase.
Functions and variables use snake_case.
Types and modules use PascalCase.
Functions and variables use snake_case.

- An exported function from this module carries the full namespace and module prefix, such as ExampleGreetÂ·MathÂ·add. + An exported function from this module carries the full namespace and module prefix, such as ExampleGreetÂ·MathÂ·add.

The implementation gate

@@ -46,16 +52,16 @@ To achieve the single-file source pattern, the code relies on two preprocessor constructs:

Include Guard: The entire file is wrapped in an include guard using the Â·ONCE suffix. This prevents redeclaration errors if the file is included multiple times.
Implementation Block: The definitions are wrapped in a single #ifdef block using the exact namespace and module name. The build system dynamically injects this macro via a -D compiler flag when building the module's specific object file.
Include Guard: The entire file is wrapped in an include guard using the Â·ONCE suffix. This prevents redeclaration errors if the file is included multiple times.
Implementation Block: The definitions are wrapped in a single #ifdef block using the exact namespace and module name. The build system dynamically injects this macro via a -D compiler flag when building the module's specific object file.

Build system mechanics

- When a consumer file, such as hello.CLI.c, contains #include "Math.lib.c", the compiler processes the file without the ExampleGreetÂ·Math macro defined. It skips the implementation and reads only the function prototype. + When a consumer file, such as hello.CLI.c, contains #include "Math.lib.c", the compiler processes the file without the ExampleGreetÂ·Math macro defined. It skips the implementation and reads only the function prototype.

- When the orchestrator compiles the library object, it evaluates the target name and explicitly passes -DExampleGreetÂ·Math to the compiler. This unlocks the gate, compiling the machine code for the definitions into Math.lib.o. + When the orchestrator compiles the library object, it evaluates the target name and explicitly passes -DExampleGreetÂ·Math to the compiler. This unlocks the gate, compiling the machine code for the definitions into Math.lib.o.

Example: Math.lib.c

@@ -63,7 +69,7 @@ The following example demonstrates the complete structure.

- + #ifndef ExampleGreetÂ·MathÂ·ONCE #define ExampleGreetÂ·MathÂ·ONCE @@ -77,27 +83,27 @@ #endif // ExampleGreetÂ·Math #endif // ExampleGreetÂ·MathÂ·ONCE - +

Cross-module dependencies

- When one module depends on another, the developer directly includes the library source file. For example, if the Greeter module requires the Math module, the file Greeter.lib.c will contain: + When one module depends on another, the developer directly includes the library source file. For example, if the Greeter module requires the Math module, the file Greeter.lib.c will contain:

- + #include "Math.lib.c" - +

- Because every file is protected by a Â·ONCE include guard, it is safe for multiple modules to include the same dependency. The preprocessor will expand the interface once per translation unit. + Because every file is protected by a Â·ONCE include guard, it is safe for multiple modules to include the same dependency. The preprocessor will expand the interface once per translation unit.

Information hiding

- To define internal helper functions or private data that should not be exposed in the module's public interface, a programmer places them strictly inside the #ifdef implementation block. + To define internal helper functions or private data that should not be exposed in the module's public interface, a programmer places them strictly inside the #ifdef implementation block.

- To prevent these internal symbols from leaking into the global namespace during linking, they must be given internal linkage. The RT skeleton provides the Local macro (defined as static in RT_global.h) for this exact purpose. + To prevent these internal symbols from leaking into the global namespace during linking, they must be given internal linkage. The RT skeleton provides the Local macro (defined as static in RT_global.h) for this exact purpose.

- + #ifdef ExampleGreetÂ·Math Local int internal_helper(int val){ @@ -109,47 +115,47 @@ } #endif // ExampleGreetÂ·Math - +

Executable entry points

- Programs intended to be compiled into standalone executables use the .CLI.c suffix. These files consume the library modules but do not define their own namespaces or include guards, as they are never included by other files. + Programs intended to be compiled into standalone executables use the .CLI.c suffix. These files consume the library modules but do not define their own namespaces or include guards, as they are never included by other files.

- A .CLI.c file includes the necessary .lib.c files, parses command-line arguments in the main function, and passes native data types to a dedicated CLI() function to orchestrate the core logic. + A .CLI.c file includes the necessary .lib.c files, parses command-line arguments in the main function, and passes native data types to a dedicated CLI() function to orchestrate the core logic.

Directory structure and namespaces

- The physical layout of the authored directory dictates how the build orchestrator finds the source code. + The physical layout of the authored directory dictates how the build orchestrator finds the source code.

Flat Structure: If a project does not utilize namespaces, the .lib.c and .CLI.c files reside directly inside the developer/authored/ directory.
Namespaced Structure: If a project utilizes namespaces, the files are grouped into subdirectories matching the namespace name, such as developer/authored/ExampleGreet/.
Flat Structure: If a project does not utilize namespaces, the .lib.c and .CLI.c files reside directly inside the developer/authored/ directory.
Namespaced Structure: If a project utilizes namespaces, the files are grouped into subdirectories matching the namespace name, such as developer/authored/ExampleGreet/.

Making the code

- The developer compiles the code using the make wrapper script located in developer/tool/make. This script accepts two primary arguments: the build command and the target namespace. + The developer compiles the code using the make wrapper script located in developer/tool/make. This script accepts two primary arguments: the build command and the target namespace.

- + > make <command> [namespace] - +

- To build the ExampleGreet code, a person issues the following command from the developer workspace: + To build the ExampleGreet code, a person issues the following command from the developer workspace:

- + > make all ExampleGreet - +

- Behind the scenes, the make wrapper assigns the namespace to an environment variable and calls the master orchestrator makefile. The orchestrator detects the namespace, updates the source directory search path to authored/ExampleGreet, and injects the appropriate namespace macros during compilation. + Behind the scenes, the make wrapper assigns the namespace to an environment variable and calls the master orchestrator makefile. The orchestrator detects the namespace, updates the source directory search path to authored/ExampleGreet, and injects the appropriate namespace macros during compilation.

- The orchestrator compiles the .lib.c files into object files under scratchpad/build/object/, archives them into a library file, and links the .CLI.c objects into standalone executables. The final artifacts are placed in the scratchpad/made/ directory. + The orchestrator compiles the .lib.c files into object files under scratchpad/build/object/, archives them into a library file, and links the .CLI.c objects into standalone executables. The final artifacts are placed in the scratchpad/made/ directory.

Promoting the artifacts

@@ -157,14 +163,14 @@ Artifacts resting in the scratchpad are volatile and private to the developer. To share the executables and libraries with the rest of the project (such as the tester or consumer roles), the developer must promote them.

- + > promote write - +

- The promote tool compares the contents of developer/scratchpad/made/ against consumer/made/. It atomically copies any new or updated files to the consumer workspace, stripping write permissions to enforce the immutability of the deployment target. Once promoted, the hello executable is ready for testing. + The promote tool compares the contents of developer/scratchpad/made/ against consumer/made/. It atomically copies any new or updated files to the consumer workspace, stripping write permissions to enforce the immutability of the deployment target. Once promoted, the hello executable is ready for testing.

- + diff --git a/document/RT-Manuscript_locator.js b/document/RT-Manuscript_locator.js new file mode 100644 index 0000000..704752b --- /dev/null +++ b/document/RT-Manuscript_locator.js @@ -0,0 +1,51 @@ +/* + indirect.js + + We have four scenarios + + immediate - used in the RT-Style distribution itself (authored, consumer, staged) + direct - used in the RT-Style project itself, but not in the distribution + indirect - the version all Harmony projects use + URL-only - always pulls style through a URL, a webserver must be present + +*/ + +window.RT = window.RT || {}; + +// --- Configuration --- +// Define the consumer project name to allow dynamic local file:// calculation. +window.RT.project_name = "Harmony"; + +// Fallback URL when served over a network where the project root is not in the URI. +window.RT.server_url = "http://localhost:8000/shared/linked-project/RT-Style/Manuscript"; + +(function() { + let style_path = window.RT.server_url; + + if (window.RT.project_name) { + const path = window.location.pathname; + const project_root_index = path.indexOf('/' + window.RT.project_name + '/'); + + if (project_root_index !== -1) { + // substring(0, stop) extracts up to the project name, leaving off the trailing slash. + // We append the explicit forward slash before navigating into the shared boundary. + const absolute_project_root = path.substring(0, project_root_index + window.RT.project_name.length + 1); + + // The symlink 'RT-Style' already drops us inside the 'consumer/' directory, + // so we proceed directly to 'Manuscript'. + style_path = absolute_project_root + "/shared/linked-project/RT-Style/Manuscript"; + } else { + console.warn("RT-Style: Cannot locate project root '/" + window.RT.project_name + "/' in URI. Falling back to server_url."); + } + } + + window.RT.dirpr_library = style_path; + + document.write( + ' + - - + + - + - +

Purpose

@@ -37,11 +41,11 @@

Clone the Harmony project to a local directory.
Remove the .git tree.
Remove the .git tree.
Rename the Harmony directory to the name of the new project.
Rename the 0pus_Harmony file to reflect the name of the new project.
Add a line to the shared/tool/version file for the new project.
git init -b core_developer_branch
Rename the 0pus_Harmony file to reflect the name of the new project.
Add a line to the shared/tool/version file for the new project.
git init -b core_developer_branch

@@ -51,7 +55,7 @@ Leave the Harmony skeleton version in the version file, so that project administrators can understand what has changed in the skeleton over time.

- The core_developer_branch is the branch that the core development team works on. Project releases are moved to release branches. + The core_developer_branch is the branch that the core development team works on. Project releases are moved to release branches.

Environment setup

@@ -59,61 +63,61 @@ Python programmers who use virtual environments will be familiar with an analogous process. The term 'virtual environment' does not invoke any hardware virtualization features; rather, it is a local environment setup. To avoid confusion, a Harmony user refers instead to the 'project setup'. The command to establish the environment is called 'setup' instead of 'activate'. Also note that in Harmony, unlike in Python, there are multiple setups available, each tailored to the specific role a person takes on.

- As of the time of this writing, the defined roles are: administrator, consumer, developer, and tester. A person takes on a role by sourcing the top-level setup script and giving the target role as an argument. For example, in a bash shell with > as the prompt, the command is: + As of the time of this writing, the defined roles are: administrator, consumer, developer, and tester. A person takes on a role by sourcing the top-level setup script and giving the target role as an argument. For example, in a bash shell with > as the prompt, the command is:

- + > . setup <role> - +

Specifically for the developer role:

- + > . setup developer - +

For the administrator role:

- + > . setup administrator - +

- Instead of starting with a period, the source command can be spelled out explicitly, for example: + Instead of starting with a period, the source command can be spelled out explicitly, for example:

- + > source setup tester - +

- Behind the scenes, the setup script performs the following actions: + Behind the scenes, the setup script performs the following actions:

Sources the project-wide setup (shared/tool/setup) to establish the core environment variables (e.g., REPO_HOME and PROJECT).
Conditionally sources shared/authored/setup (if present) to apply administrator-injected, project-specific tool configurations.
Dynamically sources all .init files found in the shared/linked-project/ directory.
Configures the PATH to include shared tools, library environments, and the specific <role>/tool directory.
Sources the project-wide setup (shared/tool/setup) to establish the core environment variables (e.g., REPO_HOME and PROJECT).
Conditionally sources shared/authored/setup (if present) to apply administrator-injected, project-specific tool configurations.
Dynamically sources all .init files found in the shared/linked-project/ directory.
Configures the PATH to include shared tools, library environments, and the specific <role>/tool directory.
Changes the working directory into the specified role's workspace.
Sources the <role>/tool/setup script. While the earlier steps apply the standard Harmony skeleton setup, this final step applies the role setup that is customized for this specific project.
Sources the <role>/tool/setup script. While the earlier steps apply the standard Harmony skeleton setup, this final step applies the role setup that is customized for this specific project.

After git clone

- Because git does not track certain artifact directories (such as consumer/ outputs), a freshly cloned repository lacks external dependencies and consumable products. Team members must perform a few steps to populate these areas. + Because git does not track certain artifact directories (such as consumer/ outputs), a freshly cloned repository lacks external dependencies and consumable products. Team members must perform a few steps to populate these areas.

Third-party tools

- Harmony is language agnostic. When a project makes use of project-specific C, Python, NodeJS, Java, or other tools, the project administrator configures the project to expect these tools in the shared/linked-project directory via the `.init` plugin system. + Harmony is language agnostic. When a project makes use of project-specific C, Python, NodeJS, Java, or other tools, the project administrator configures the project to expect these tools in the shared/linked-project directory via the `.init` plugin system.

- Because multiple team members will have to repeat the third-party install process after cloning a project, the administrator should carefully document the installation steps and place the resulting documents in the administrator/document directory. The standard installation method is to clone the external tool into the parent directory alongside the project, create a symlink to it under shared/linked-project/ using the project/ parent link, and supply an .init script to manage the local environment variables. + Because multiple team members will have to repeat the third-party install process after cloning a project, the administrator should carefully document the installation steps and place the resulting documents in the administrator/document directory. The standard installation method is to clone the external tool into the parent directory alongside the project, create a symlink to it under shared/linked-project/ using the project/ parent link, and supply an .init script to manage the local environment variables.

Consumer build

@@ -121,10 +125,10 @@ In this section we use the term 'consumer' to mean any team member that wants to make use of the project work product. The tester will want to test it, and the consumer role will want to deploy it, etc.

- Because compiled binaries and final layouts are not tracked in the repository, the current version of Harmony requires a work product consumer to run a local build after cloning the project. The results of the build will appear directly in the consumer/ directory. + Because compiled binaries and final layouts are not tracked in the repository, the current version of Harmony requires a work product consumer to run a local build after cloning the project. The results of the build will appear directly in the consumer/ directory.

- To facilitate this, the developer must explicitly document the project's build and promote procedure, saving this guide as developer/document/build.html. The consumer must then read this document and execute the described steps to locally populate their consumer/ directory. + To facilitate this, the developer must explicitly document the project's build and promote procedure, saving this guide as developer/document/build.html. The consumer must then read this document and execute the described steps to locally populate their consumer/ directory.

@@ -132,19 +136,19 @@

> bash
> cd <project>
> . setup developer
> build <namespace>
> promote write
> exit
> bash
> cd <project>
> . setup <role>
> bash
> cd <project>
> . setup developer
> build <namespace>
> promote write
> exit
> bash
> cd <project>
> . setup <role>

- This sequence opens a bash shell, assumes the developer role to orchestrate the build, makes the work product, then promotes it to the consumer's workspace. The exit command drops the developer role. The last two lines put the person into the <role> workspace, typically for testing or deploying. + This sequence opens a bash shell, assumes the developer role to orchestrate the build, makes the work product, then promotes it to the consumer's workspace. The exit command drops the developer role. The last two lines put the person into the <role> workspace, typically for testing or deploying.

@@ -153,10 +157,10 @@ This section discusses our thinking in naming the files and directories found in the Harmony skeleton.

- A directory name is considered to be a property given to each file contained in the directory. A full path then forms a semantic sentence describing each file. + A directory name is considered to be a property given to each file contained in the directory. A full path then forms a semantic sentence describing each file.

- Because a directory name represents a property, it is rarely plural. For example, when each and every file in a directory is a test, the directory is named test. + Because a directory name represents a property, it is rarely plural. For example, when each and every file in a directory is a test, the directory is named test.

We run into limitations when using a conventional file system as though it were a property based file system. One limitation is that we are forced to choose a single directory name for each file. When a set of files in a directory all share the same multiple properties, we can use a compound directory name with the properties separated by an underscore, but it is impractical to specify overlapping directory groupings, i.e. we can't arbitrarily define any number of properties for a file in this manner. @@ -165,41 +169,41 @@ The following list presents each property type in order of preference when naming directories:

Role Association (administrator, developer, tester, consumer): Identifies the persona, whether human or AI, intended to interact with the files.
Provenance (authored, made): Indicates whether the file was created by an intellect or mechanically produced by a tool.
Capability (tool, document, experiment): Describes the primary function or structural nature of the file.
Lifecycle State (scratchpad, stage): Denotes the persistence, volatility, or promotion status of the file.
Tracking Status (tracked, untracked): Specifies the version control expectations for the artifacts.
Role Association (administrator, developer, tester, consumer): Identifies the persona, whether human or AI, intended to interact with the files.
Provenance (authored, made): Indicates whether the file was created by an intellect or mechanically produced by a tool.
Capability (tool, document, experiment): Describes the primary function or structural nature of the file.
Lifecycle State (scratchpad, stage): Denotes the persistence, volatility, or promotion status of the file.
Tracking Status (tracked, untracked): Specifies the version control expectations for the artifacts.

Authored, made, scratchpad, inherited

- Files found in a directory named authored were written by project team members. They did not come with the Harmony skeleton, nor with the installation of other software. Project build tools treat authored directories as strictly read-only. Typically these files constitute the intellectual property of a project. + Files found in a directory named authored were written by project team members. They did not come with the Harmony skeleton, nor with the installation of other software. Project build tools treat authored directories as strictly read-only. Typically these files constitute the intellectual property of a project.

- All source code that gets built into a promotion or project release must be placed in the developers' authored directory. The story is not as clean for build tools and other files. New documents go into document directories, and new tools go into the tool directories, etc. As a specific example, the developer will almost certainly edit the developer/tool/build file. + All source code that gets built into a promotion or project release must be placed in the developers' authored directory. The story is not as clean for build tools and other files. New documents go into document directories, and new tools go into the tool directories, etc. As a specific example, the developer will almost certainly edit the developer/tool/build file.

- When the Harmony version line in the shared/tool/version file is left in place, it is straightforward for a project administrator to determine which Harmony skeleton files have been edited in a project, and which new files have been added. + When the Harmony version line in the shared/tool/version file is left in place, it is straightforward for a project administrator to determine which Harmony skeleton files have been edited in a project, and which new files have been added.

- Files found in a directory named scratchpad are not tracked. Hence, a git clone will always return empty scratchpad directories. It is common for tools to place intermediate files on a scratchpad. It is also common for files to be staged on a scratchpad. Tools play nice and use subdirectories on the pad, so a person who is aware of those subdirectory names can use a scratchpad as a temporary directory. There is a scratchpad maintenance tool that comes with the Harmony, called unimaginatively, scratchpad. Pay attention as one of its commands is clear, and that deletes everything on the current directory's scratchpad. + Files found in a directory named scratchpad are not tracked. Hence, a git clone will always return empty scratchpad directories. It is common for tools to place intermediate files on a scratchpad. It is also common for files to be staged on a scratchpad. Tools play nice and use subdirectories on the pad, so a person who is aware of those subdirectory names can use a scratchpad as a temporary directory. There is a scratchpad maintenance tool that comes with the Harmony, called unimaginatively, scratchpad. Pay attention as one of its commands is clear, and that deletes everything on the current directory's scratchpad.

- Third party software is installed under shared/linked-project. Other files are said to be inherited, or to be customizations. + Third party software is installed under shared/linked-project. Other files are said to be inherited, or to be customizations.

Top-level repository layout

- A team member will source the project setup file to take on a role. As of this writing, the supported roles are: administrator, developer, tester, and consumer. + A team member will source the project setup file to take on a role. As of this writing, the supported roles are: administrator, developer, tester, and consumer.

administrator/ : Project-local tools and skeleton maintenance.
developer/ : Primary workspace for developers.
tester/ : Regression and validation workspace for testers.
consumer/ : Consumption workspace acting as the final artifact sink.
shared/ : Shared ecosystem tools and global environments.
administrator/ : Project-local tools and skeleton maintenance.
developer/ : Primary workspace for developers.
tester/ : Regression and validation workspace for testers.
consumer/ : Consumption workspace acting as the final artifact sink.
shared/ : Shared ecosystem tools and global environments.

The administrator work area

@@ -209,29 +213,29 @@

The developer work area

- This directory is entered by first going to the top-level directory of the project, then sourcing . setup developer. + This directory is entered by first going to the top-level directory of the project, then sourcing . setup developer.

authored/ : Human-written source. Tracked by Git.
made/ : Tracked artifacts generated by tools (e.g., links to CLI entry points).
experiment/ : Try-it-here code. Short-lived spot testing.
scratchpad/ : Git-ignored directory. Holds all intermediate build outputs, including the staged namespace directories for promotions.
tool/ : Developer-specific tools (like the promote and build scripts).
authored/ : Human-written source. Tracked by Git.
made/ : Tracked artifacts generated by tools (e.g., links to CLI entry points).
experiment/ : Try-it-here code. Short-lived spot testing.
scratchpad/ : Git-ignored directory. Holds all intermediate build outputs, including the staged namespace directories for promotions.
tool/ : Developer-specific tools (like the promote and build scripts).

The tester work area

- This directory is dedicated to formal testing, including regression suites. While a developer can run and keep informal spot tests in their experiment/ directory, any experiment promoted to a formal test is moved here. This enforces the boundary between writing code and validating it. + This directory is dedicated to formal testing, including regression suites. While a developer can run and keep informal spot tests in their experiment/ directory, any experiment promoted to a formal test is moved here. This enforces the boundary between writing code and validating it.

The shared tree

- This directory contains ecosystem tools and global environments available to all roles. This includes the shared tool directory, as well as third-party symlinks and .init scripts required by the project. To assist in project specific modifications to the Harmony skeleton, Harmony comes with an empty shared/authored directory that is listed earlier in the executable search path than shared/tool. + This directory contains ecosystem tools and global environments available to all roles. This includes the shared tool directory, as well as third-party symlinks and .init scripts required by the project. To assist in project specific modifications to the Harmony skeleton, Harmony comes with an empty shared/authored directory that is listed earlier in the executable search path than shared/tool.

The consumer tree

- The consumer/ tree is where developers put work product that is ready to be consumed. The entire directory is git-ignored and treated as a transient deployment target. Artifacts arrive in the consumer/ tree only when the promote script is invoked, which performs a flat-copy from the developer's scratchpad/made directory. + The consumer/ tree is where developers put work product that is ready to be consumed. The entire directory is git-ignored and treated as a transient deployment target. Artifacts arrive in the consumer/ tree only when the promote script is invoked, which performs a flat-copy from the developer's scratchpad/made directory.

Document directories

@@ -239,23 +243,23 @@ There is a directory for documents that talks about the project as a whole, one for each role, one for tools that are shared among the roles, and the released work product probably comes with a document directory of its own.

document/ : Top-level onboarding, project-wide structure, such as this document.
consumer/<namespace>/document/ : Documentation for end-users of made code (e.g., man pages, application manuals, library API references).
administrator/document/ : Documentation for maintaining the project skeleton and global tools.
developer/document/ : Documentation for developers, including coding standards and internal API guides.
tester/document/ : Documentation for testers detailing test plans and tools.
shared/document/ : Documentation on installing and configuring shared tools.
document/ : Top-level onboarding, project-wide structure, such as this document.
consumer/<namespace>/document/ : Documentation for end-users of made code (e.g., man pages, application manuals, library API references).
administrator/document/ : Documentation for maintaining the project skeleton and global tools.
developer/document/ : Documentation for developers, including coding standards and internal API guides.
tester/document/ : Documentation for testers detailing test plans and tools.
shared/document/ : Documentation on installing and configuring shared tools.

- Currently, our developers write documents directly in HTML using the RT semantic tags. See the RT-Style project and the documentation there. A common approach is to copy another document and the setup.js file, then to type over the top of that other document. + Currently, our developers write documents directly in HTML using the RT semantic tags. See the RTÂ·Style project and the documentation there. A common approach is to copy another document and the setup.js file, then to type over the top of that other document.

Untracked directories

consumer/ (Excluding the base .gitignore)
shared/linked-project/ (Excluding .init and .gitignore files)
**/scratchpad/
consumer/ (Excluding the base .gitignore)
shared/linked-project/ (Excluding .init and .gitignore files)
**/scratchpad/

Workflow

@@ -263,21 +267,21 @@

Developer promotion and project releases

- As a first step, a developer creates a promotion candidate inside of the consumer/ directory. This is typically done by running build to stage the artifacts into scratchpad/made, followed by running promote write. The developer will often modify the versions of one or both of those tools that come with the Harmony skeleton. The promotion candidate remains stable until the next promotion. + As a first step, a developer creates a promotion candidate inside of the consumer/ directory. This is typically done by running build to stage the artifacts into scratchpad/made, followed by running promote write. The developer will often modify the versions of one or both of those tools that come with the Harmony skeleton. The promotion candidate remains stable until the next promotion.

- Then the tester runs tests on the promotion candidate. Tests must only read from the consumer/ directory, though local copies can be made and edited as experiments. + Then the tester runs tests on the promotion candidate. Tests must only read from the consumer/ directory, though local copies can be made and edited as experiments.

It is common for a developer to open a second window on his desktop, and then enter the project as a tester in that second window. The developer can then make a promotion candidate, run the tests, edit source code, and perhaps tests, and then quickly spin through the test-debug-fix-promote cycle repeatedly.

- When the product manager determines the work product to be sufficiently reliable and feature rich, the administrator will make a project release. He will do this by creating a branch called release_v<major> and tagging it. The major release numbers go up incrementally. + When the product manager determines the work product to be sufficiently reliable and feature rich, the administrator will make a project release. He will do this by creating a branch called release_v<major> and tagging it. The major release numbers go up incrementally.

The Harmony directory tree

- + 2026-06-23 13:41:45 Z [Harmony:administrator] Thomas_developer@StanleyPark Â§/home/Thomas/subu_data/developer/projectÂ§ > tree Harmony @@ -329,8 +333,8 @@ â â âââ project -> ../../../ â â âââ Python-3.12.3 -> project/Python-3.12.3 â â âââ Python.init - â â âââ RT-Style -> project/RT-Style/consumer - â â âââ RT-Style.init + â â âââ RTÂ·Style -> project/RTÂ·Style/consumer + â â âââ RTÂ·Style.init â âââ tool â âââ scratchpad â âââ setup @@ -341,13 +345,13 @@ â âââ test_routine.sh âââ RT_Format â âââ RT_Format - â âââ RT-formatter.el + â âââ RTÂ·formatter.el â âââ data_test-0.c â âââ data_test-1.py âââ tool âââ setup - + - + diff --git a/document/role-and-workflow_product-development.html b/document/role-and-workflow_product-development.html index 2a4f655..bede081 100644 --- a/document/role-and-workflow_product-development.html +++ b/document/role-and-workflow_product-development.html @@ -3,20 +3,24 @@ Product development roles and workflow - + - - + + - + - +

Roles as hats

@@ -27,12 +31,12 @@

These roles interact directly with the repository. To enter a workspace, change directory to the top-level of the project and source the setup file for the desired role:

- + > . setup administrator > . setup developer > . setup tester > . setup consumer - +

It is common for a person to have multiple terminal sessions or IDEs open, each running under a different role environment.

@@ -41,23 +45,23 @@

Responsibilities:

Set up the project directory and keep it in sync with the Harmony skeleton.
Maintain role environments (apart from role-specific tool/setup files).
Maintain role environments (apart from role-specific tool/setup files).
Install and maintain shared and third_party tools, addressing issues with the project workflow. Note that the term "third_party" encompasses any software not authored within this specific project.

Developer role

Responsibilities and Boundaries:

Write and modify authored/ source.
Run builds and place artifacts in scratchpad/made, then execute the promote write script to copy artifacts to consumer/made for testing.
Run experiments in experiment/. These experiments can sometimes be promoted to formal tests, but there is no requirement to do so. The developer role should not blur into the tester role; experiments are informal, whereas tests are formal and retained.
Strict Boundary: A developer never writes into the tester/ directory. Instead, a developer adds tests to developer/experiment/ and offers to share them.
Write and modify authored/ source.
Run builds and place artifacts in scratchpad/made, then execute the promote write script to copy artifacts to consumer/made for testing.
Run experiments in experiment/. These experiments can sometimes be promoted to formal tests, but there is no requirement to do so. The developer role should not blur into the tester role; experiments are informal, whereas tests are formal and retained.
Strict Boundary: A developer never writes into the tester/ directory. Instead, a developer adds tests to developer/experiment/ and offers to share them.

Tester role

Responsibilities and Boundaries:

Evaluate candidates under consumer/made/ and run regression suites to confirm: +
Evaluate candidates under consumer/made/ and run regression suites to confirm:
- That the code does not crash.
- That consumers do not have a bad experience.
File issues and communicate feedback to the developers.
Strict Boundary: A tester never patches code in the developer/ directory. Instead, the tester files issues or proposes code fixes on a separate branch.
Strict Boundary: A tester never patches code in the developer/ directory. Instead, the tester files issues or proposes code fixes on a separate branch.

Consumer role

Responsibilities:

Act as the end-user simulation environment.
Consume and deploy artifacts exclusively from the consumer/made/ target.
Consume and deploy artifacts exclusively from the consumer/made/ target.
Never author or modify code; strictly run local builds or deployments for architecture-specific testing.
Report issues. (Anyone can report an issue, and consumers regularly do).

External roles

- These roles drive the project forward but do not have a dedicated setup <role> workspace, as they do not directly build or test the code in that capacity. If these individuals need to interface with the code, they simply put on a workspace role hat, such as administer, developer, tester, or consumer. + These roles drive the project forward but do not have a dedicated setup <role> workspace, as they do not directly build or test the code in that capacity. If these individuals need to interface with the code, they simply put on a workspace role hat, such as administer, developer, tester, or consumer.

Product manager

@@ -111,12 +115,12 @@

Promotion mechanics

- Building and promotion are separate activities. The developer compiles and places files in developer/scratchpad/made. The developer then runs promote write to transfer those files to consumer/made. + Building and promotion are separate activities. The developer compiles and places files in developer/scratchpad/made. The developer then runs promote write to transfer those files to consumer/made.

- The consumer/made directory is strictly an untracked deployment target. No tools are permitted to rebuild during promotion, and no builds are run directly inside the consumer made directory. + The consumer/made directory is strictly an untracked deployment target. No tools are permitted to rebuild during promotion, and no builds are run directly inside the consumer made directory.

- + diff --git a/document/role-and-workflow_product-maintenance.html b/document/role-and-workflow_product-maintenance.html index 1f76dd0..803e132 100644 --- a/document/role-and-workflow_product-maintenance.html +++ b/document/role-and-workflow_product-maintenance.html @@ -3,20 +3,24 @@ Product maintenance roles and workflow - + - - + + - + - +

Maintenance philosophy

@@ -39,7 +43,7 @@

- The tester team develops and maintains the regression suite, the reliability suite, and additional tests. + The tester team develops and maintains the regression suite, the reliability suite, and additional tests.

@@ -69,7 +73,7 @@

Core developer queue

- This queue serves the core_developer_branch. A tester writes a test for every issue reported in this queue. Doing so isolates the defect, proves the fix, and guards against future regressions. + This queue serves the core_developer_branch. A tester writes a test for every issue reported in this queue. Doing so isolates the defect, proves the fix, and guards against future regressions.

Released product queue

@@ -79,7 +83,7 @@

Triage and patching

- Guided by the project philosophy, the triage team reviews each release queue issue to determine its impact. The team assesses whether the defect affects the core_developer_branch, assuming by default that it probably does. The team also determines if the defect is critical enough to warrant a patch on one or more active release branches. + Guided by the project philosophy, the triage team reviews each release queue issue to determine its impact. The team assesses whether the defect affects the core_developer_branch, assuming by default that it probably does. The team also determines if the defect is critical enough to warrant a patch on one or more active release branches.

Based on this assessment, the triage team files actionable tickets in the core developer queue. A ticket explicitly specifies its target branches. A ticket will be filed against either the core developer branch, specific release branches, or a combination of both. @@ -88,12 +92,12 @@ Members of the tester team also file tickets directly into the core developer queue when they discover defects in the core branch.

- Responsibility for resolving a ticket depends on its target. The core developer team addresses fixes required on the core_developer_branch. The branch maintenance team addresses fixes required on the release_v<major> branches. + Responsibility for resolving a ticket depends on its target. The core developer team addresses fixes required on the core_developer_branch. The branch maintenance team addresses fixes required on the release_v<major> branches.

- When a release is patched, the branch name remains static. The administrator advances the minor release number in the shared/tool/version file and tags the commit. + When a release is patched, the branch name remains static. The administrator advances the minor release number in the shared/tool/version file and tags the commit.

- + diff --git a/shared/document/RT-Manuscript_locator.js b/shared/document/RT-Manuscript_locator.js new file mode 100644 index 0000000..39b2706 --- /dev/null +++ b/shared/document/RT-Manuscript_locator.js @@ -0,0 +1,54 @@ +/* + We have four scenarios + + immediate - used in the RT-Style distribution itself (authored, consumer, staged) + direct - used in the RT-Style project itself, but not in the distribution + indirect - the version all Harmony projects use + URL-only - always pulls style through a URL, a webserver must be present + +*/ + +window.RT = window.RT || {}; + +// --- Configuration --- +// Define the consumer project name to allow dynamic local file:// calculation. +window.RT.project_name = "Harmony"; + +// Fallback URL when served over a network where the project root is not in the URI. +window.RT.server_url = "http://localhost:8000/shared/linked-project/RT-Style/Manuscript"; + +(function() { + let style_path = window.RT.server_url; + + if (window.RT.project_name) { + const path = window.location.pathname; + const project_root_index = path.indexOf('/' + window.RT.project_name + '/'); + + if (project_root_index !== -1) { + // substring(0, stop) extracts up to the project name, leaving off the trailing slash. + // We append the explicit forward slash before navigating into the shared boundary. + const absolute_project_root = path.substring(0, project_root_index + window.RT.project_name.length + 1); + + // The symlink 'RT-Style' already drops us inside the 'consumer/' directory, + // so we proceed directly to 'Manuscript'. + style_path = absolute_project_root + "/shared/linked-project/RT-Style/Manuscript"; + } else { + console.warn("RT-Style: Cannot locate project root '/" + window.RT.project_name + "/' in URI. Falling back to server_url."); + } + } + + window.RT.dirpr_library = style_path; + + // 1. Inject the loader script + document.write('