Metadata-Version: 2.4
Name: phios
Version: 1.0.0
Summary: PhiOS sovereign shell for local-first coherent computing
License:                     GNU GENERAL PUBLIC LICENSE
                               Version 3, 29 June 2007
        
         Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
         Everyone is permitted to copy and distribute verbatim copies
         of this license document, but changing it is not allowed.
        
                                    Preamble
        
          The GNU General Public License is a free, copyleft license for
        software and other kinds of works.
        
          The licenses for most software and other practical works are designed
        to take away your freedom to share and change the works.  By contrast,
        the GNU General Public License is intended to guarantee your freedom to
        share and change all versions of a program--to make sure it remains free
        software for all its users.  We, the Free Software Foundation, use the
        GNU General Public License for most of our software; it applies also to
        any other work released this way by its authors.  You can apply it to
        your programs, too.
        
          When we speak of free software, we are referring to freedom, not
        price.  Our General Public Licenses are designed to make sure that you
        have the freedom to distribute copies of free software (and charge for
        them if you wish), that you receive source code or can get it if you
        want it, that you can change the software or use pieces of it in new
        free programs, and that you know you can do these things.
        
          To protect your rights, we need to prevent others from denying you
        these rights or asking you to surrender the rights.  Therefore, you have
        certain responsibilities if you distribute copies of the software, or if
        you modify it: responsibilities to respect the freedom of others.
        
          For example, if you distribute copies of such a program, whether
        gratis or for a fee, you must pass on to the recipients the same
        freedoms that you received.  You must make sure that they, too, receive
        or can get the source code.  And you must show them these terms so they
        know their rights.
        
          Developers that use the GNU GPL protect your rights with two steps:
        (1) assert copyright on the software, and (2) offer you this License
        giving you legal permission to copy, distribute and/or modify it.
        
          For the developers' and authors' protection, the GPL clearly explains
        that there is no warranty for this free software.  For both users' and
        authors' sake, the GPL requires that modified versions be marked as
        changed, so that their problems will not be attributed erroneously to
        authors of previous versions.
        
          Some devices are designed to deny users access to install or run
        modified versions of the software inside them, although the manufacturer
        can do so.  This is fundamentally incompatible with the aim of
        protecting users' freedom to change the software.  The systematic
        pattern of such abuse occurs in the area of products for individuals to
        use, which is precisely where it is most unacceptable.  Therefore, we
        have designed this version of the GPL to prohibit the practice for those
        products.  If such problems arise substantially in other domains, we
        stand ready to extend this provision to those domains in future versions
        of the GPL, as needed to protect the freedom of users.
        
          Finally, every program is threatened constantly by software patents.
        States should not allow patents to restrict development and use of
        software on general-purpose computers, but in those that do, we wish to
        avoid the special danger that patents applied to a free program could
        make it effectively proprietary.  To prevent this, the GPL assures that
        patents cannot be used to render the program non-free.
        
          The precise terms and conditions for copying, distribution and
        modification follow.
        
                               TERMS AND CONDITIONS
        
          0. Definitions.
        
          "This License" refers to version 3 of the GNU General Public License.
        
          "Copyright" also means copyright-like laws that apply to other kinds of
        works, such as semiconductor masks.
        
          "The Program" refers to any copyrightable work licensed under this
        License.  Each licensee is addressed as "you".  "Licensees" and
        "recipients" may be individuals or organizations.
        
          To "modify" a work means to copy from or adapt all or part of the work
        in a fashion requiring copyright permission, other than the making of an
        exact copy.  The resulting work is called a "modified version" of the
        earlier work or a work "based on" the earlier work.
        
          A "covered work" means either the unmodified Program or a work based
        on the Program.
        
          To "propagate" a work means to do anything with it that, without
        permission, would make you directly or secondarily liable for
        infringement under applicable copyright law, except executing it on a
        computer or modifying a private copy.  Propagation includes copying,
        distribution (with or without modification), making available to the
        public, and in some countries other activities as well.
        
          To "convey" a work means any kind of propagation that enables other
        parties to make or receive copies.  Mere interaction with a user through
        a computer network, with no transfer of a copy, is not conveying.
        
          An interactive user interface displays "Appropriate Legal Notices"
        to the extent that it includes a convenient and prominently visible
        feature that (1) displays an appropriate copyright notice, and (2)
        tells the user that there is no warranty for the work (except to the
        extent that warranties are provided), that licensees may convey the
        work under this License, and how to view a copy of this License.  If
        the interface presents a list of user commands or options, such as a
        menu, a prominent item in the list meets this criterion.
        
          1. Source Code.
        
          The "source code" for a work means the preferred form of the work
        for making modifications to it.  "Object code" means any non-source
        form of a work.
        
          A "Standard Interface" means an interface that either is an official
        standard defined by a recognized standards body, or, in the case of
        interfaces specified for a particular programming language, one that
        is widely used among developers working in that language.
        
          The "System Libraries" of an executable work include anything, other
        than the work as a whole, that (a) is included in the normal form of
        packaging a Major Component, but which is not part of that Major
        Component, and (b) serves only to enable use of the work with that
        Major Component, or to implement a Standard Interface for which an
        implementation is available to the public in source code form.  A
        "Major Component", in this context, means a major essential component
        (kernel, window system, and so on) of the specific operating system
        (if any) on which the executable work runs, or a compiler used to
        produce the work, or an object code interpreter used to run it.
        
          The "Corresponding Source" for a work in object code form means all
        the source code needed to generate, install, and (for an executable
        work) run the object code and to modify the work, including scripts to
        control those activities.  However, it does not include the work's
        System Libraries, or general-purpose tools or generally available free
        programs which are used unmodified in performing those activities but
        which are not part of the work.  For example, Corresponding Source
        includes interface definition files associated with source files for
        the work, and the source code for shared libraries and dynamically
        linked subprograms that the work is specifically designed to require,
        such as by intimate data communication or control flow between those
        subprograms and other parts of the work.
        
          The Corresponding Source need not include anything that users
        can regenerate automatically from other parts of the Corresponding
        Source.
        
          The Corresponding Source for a work in source code form is that
        same work.
        
          2. Basic Permissions.
        
          All rights granted under this License are granted for the term of
        copyright on the Program, and are irrevocable provided the stated
        conditions are met.  This License explicitly affirms your unlimited
        permission to run the unmodified Program.  The output from running a
        covered work is covered by this License only if the output, given its
        content, constitutes a covered work.  This License acknowledges your
        rights of fair use or other equivalent, as provided by copyright law.
        
          You may make, run and propagate covered works that you do not
        convey, without conditions so long as your license otherwise remains
        in force.  You may convey covered works to others for the sole purpose
        of having them make modifications exclusively for you, or provide you
        with facilities for running those works, provided that you comply with
        the terms of this License in conveying all material for which you do
        not control copyright.  Those thus making or running the covered works
        for you must do so exclusively on your behalf, under your direction
        and control, on terms that prohibit them from making any copies of
        your copyrighted material outside their relationship with you.
        
          Conveying under any other circumstances is permitted solely under
        the conditions stated below.  Sublicensing is not allowed; section 10
        makes it unnecessary.
        
          3. Protecting Users' Legal Rights From Anti-Circumvention Law.
        
          No covered work shall be deemed part of an effective technological
        measure under any applicable law fulfilling obligations under article
        11 of the WIPO copyright treaty adopted on 20 December 1996, or
        similar laws prohibiting or restricting circumvention of such
        measures.
        
          When you convey a covered work, you waive any legal power to forbid
        circumvention of technological measures to the extent such circumvention
        is effected by exercising rights under this License with respect to
        the covered work, and you disclaim any intention to limit operation or
        modification of the work as a means of enforcing, against the work's
        users, your or third parties' legal rights to forbid circumvention of
        technological measures.
        
          4. Conveying Verbatim Copies.
        
          You may convey verbatim copies of the Program's source code as you
        receive it, in any medium, provided that you conspicuously and
        appropriately publish on each copy an appropriate copyright notice;
        keep intact all notices stating that this License and any
        non-permissive terms added in accord with section 7 apply to the code;
        keep intact all notices of the absence of any warranty; and give all
        recipients a copy of this License along with the Program.
        
          You may charge any price or no price for each copy that you convey,
        and you may offer support or warranty protection for a fee.
        
          5. Conveying Modified Source Versions.
        
          You may convey a work based on the Program, or the modifications to
        produce it from the Program, in the form of source code under the
        terms of section 4, provided that you also meet all of these conditions:
        
            a) The work must carry prominent notices stating that you modified
            it, and giving a relevant date.
        
            b) The work must carry prominent notices stating that it is
            released under this License and any conditions added under section
            7.  This requirement modifies the requirement in section 4 to
            "keep intact all notices".
        
            c) You must license the entire work, as a whole, under this
            License to anyone who comes into possession of a copy.  This
            License will therefore apply, along with any applicable section 7
            additional terms, to the whole of the work, and all its parts,
            regardless of how they are packaged.  This License gives no
            permission to license the work in any other way, but it does not
            invalidate such permission if you have separately received it.
        
            d) If the work has interactive user interfaces, each must display
            Appropriate Legal Notices; however, if the Program has interactive
            interfaces that do not display Appropriate Legal Notices, your
            work need not make them do so.
        
          A compilation of a covered work with other separate and independent
        works, which are not by their nature extensions of the covered work,
        and which are not combined with it such as to form a larger program,
        in or on a volume of a storage or distribution medium, is called an
        "aggregate" if the compilation and its resulting copyright are not
        used to limit the access or legal rights of the compilation's users
        beyond what the individual works permit.  Inclusion of a covered work
        in an aggregate does not cause this License to apply to the other
        parts of the aggregate.
        
          6. Conveying Non-Source Forms.
        
          You may convey a covered work in object code form under the terms
        of sections 4 and 5, provided that you also convey the
        machine-readable Corresponding Source under the terms of this License,
        in one of these ways:
        
            a) Convey the object code in, or embodied in, a physical product
            (including a physical distribution medium), accompanied by the
            Corresponding Source fixed on a durable physical medium
            customarily used for software interchange.
        
            b) Convey the object code in, or embodied in, a physical product
            (including a physical distribution medium), accompanied by a
            written offer, valid for at least three years and valid for as
            long as you offer spare parts or customer support for that product
            model, to give anyone who possesses the object code either (1) a
            copy of the Corresponding Source for all the software in the
            product that is covered by this License, on a durable physical
            medium customarily used for software interchange, for a price no
            more than your reasonable cost of physically performing this
            conveying of source, or (2) access to copy the
            Corresponding Source from a network server at no charge.
        
            c) Convey individual copies of the object code with a copy of the
            written offer to provide the Corresponding Source.  This
            alternative is allowed only occasionally and noncommercially, and
            only if you received the object code with such an offer, in accord
            with subsection 6b.
        
            d) Convey the object code by offering access from a designated
            place (gratis or for a charge), and offer equivalent access to the
            Corresponding Source in the same way through the same place at no
            further charge.  You need not require recipients to copy the
            Corresponding Source along with the object code.  If the place to
            copy the object code is a network server, the Corresponding Source
            may be on a different server (operated by you or a third party)
            that supports equivalent copying facilities, provided you maintain
            clear directions next to the object code saying where to find the
            Corresponding Source.  Regardless of what server hosts the
            Corresponding Source, you remain obligated to ensure that it is
            available for as long as needed to satisfy these requirements.
        
            e) Convey the object code using peer-to-peer transmission, provided
            you inform other peers where the object code and Corresponding
            Source of the work are being offered to the general public at no
            charge under subsection 6d.
        
          A separable portion of the object code, whose source code is excluded
        from the Corresponding Source as a System Library, need not be
        included in conveying the object code work.
        
          A "User Product" is either (1) a "consumer product", which means any
        tangible personal property which is normally used for personal, family,
        or household purposes, or (2) anything designed or sold for incorporation
        into a dwelling.  In determining whether a product is a consumer product,
        doubtful cases shall be resolved in favor of coverage.  For a particular
        product received by a particular user, "normally used" refers to a
        typical or common use of that class of product, regardless of the status
        of the particular user or of the way in which the particular user
        actually uses, or expects or is expected to use, the product.  A product
        is a consumer product regardless of whether the product has substantial
        commercial, industrial or non-consumer uses, unless such uses represent
        the only significant mode of use of the product.
        
          "Installation Information" for a User Product means any methods,
        procedures, authorization keys, or other information required to install
        and execute modified versions of a covered work in that User Product from
        a modified version of its Corresponding Source.  The information must
        suffice to ensure that the continued functioning of the modified object
        code is in no case prevented or interfered with solely because
        modification has been made.
        
          If you convey an object code work under this section in, or with, or
        specifically for use in, a User Product, and the conveying occurs as
        part of a transaction in which the right of possession and use of the
        User Product is transferred to the recipient in perpetuity or for a
        fixed term (regardless of how the transaction is characterized), the
        Corresponding Source conveyed under this section must be accompanied
        by the Installation Information.  But this requirement does not apply
        if neither you nor any third party retains the ability to install
        modified object code on the User Product (for example, the work has
        been installed in ROM).
        
          The requirement to provide Installation Information does not include a
        requirement to continue to provide support service, warranty, or updates
        for a work that has been modified or installed by the recipient, or for
        the User Product in which it has been modified or installed.  Access to a
        network may be denied when the modification itself materially and
        adversely affects the operation of the network or violates the rules and
        protocols for communication across the network.
        
          Corresponding Source conveyed, and Installation Information provided,
        in accord with this section must be in a format that is publicly
        documented (and with an implementation available to the public in
        source code form), and must require no special password or key for
        unpacking, reading or copying.
        
          7. Additional Terms.
        
          "Additional permissions" are terms that supplement the terms of this
        License by making exceptions from one or more of its conditions.
        Additional permissions that are applicable to the entire Program shall
        be treated as though they were included in this License, to the extent
        that they are valid under applicable law.  If additional permissions
        apply only to part of the Program, that part may be used separately
        under those permissions, but the entire Program remains governed by
        this License without regard to the additional permissions.
        
          When you convey a copy of a covered work, you may at your option
        remove any additional permissions from that copy, or from any part of
        it.  (Additional permissions may be written to require their own
        removal in certain cases when you modify the work.)  You may place
        additional permissions on material, added by you to a covered work,
        for which you have or can give appropriate copyright permission.
        
          Notwithstanding any other provision of this License, for material you
        add to a covered work, you may (if authorized by the copyright holders of
        that material) supplement the terms of this License with terms:
        
            a) Disclaiming warranty or limiting liability differently from the
            terms of sections 15 and 16 of this License; or
        
            b) Requiring preservation of specified reasonable legal notices or
            author attributions in that material or in the Appropriate Legal
            Notices displayed by works containing it; or
        
            c) Prohibiting misrepresentation of the origin of that material, or
            requiring that modified versions of such material be marked in
            reasonable ways as different from the original version; or
        
            d) Limiting the use for publicity purposes of names of licensors or
            authors of the material; or
        
            e) Declining to grant rights under trademark law for use of some
            trade names, trademarks, or service marks; or
        
            f) Requiring indemnification of licensors and authors of that
            material by anyone who conveys the material (or modified versions of
            it) with contractual assumptions of liability to the recipient, for
            any liability that these contractual assumptions directly impose on
            those licensors and authors.
        
          All other non-permissive additional terms are considered "further
        restrictions" within the meaning of section 10.  If the Program as you
        received it, or any part of it, contains a notice stating that it is
        governed by this License along with a term that is a further
        restriction, you may remove that term.  If a license document contains
        a further restriction but permits relicensing or conveying under this
        License, you may add to a covered work material governed by the terms
        of that license document, provided that the further restriction does
        not survive such relicensing or conveying.
        
          If you add terms to a covered work in accord with this section, you
        must place, in the relevant source files, a statement of the
        additional terms that apply to those files, or a notice indicating
        where to find the applicable terms.
        
          Additional terms, permissive or non-permissive, may be stated in the
        form of a separately written license, or stated as exceptions;
        the above requirements apply either way.
        
          8. Termination.
        
          You may not propagate or modify a covered work except as expressly
        provided under this License.  Any attempt otherwise to propagate or
        modify it is void, and will automatically terminate your rights under
        this License (including any patent licenses granted under the third
        paragraph of section 11).
        
          However, if you cease all violation of this License, then your
        license from a particular copyright holder is reinstated (a)
        provisionally, unless and until the copyright holder explicitly and
        finally terminates your license, and (b) permanently, if the copyright
        holder fails to notify you of the violation by some reasonable means
        prior to 60 days after the cessation.
        
          Moreover, your license from a particular copyright holder is
        reinstated permanently if the copyright holder notifies you of the
        violation by some reasonable means, this is the first time you have
        received notice of violation of this License (for any work) from that
        copyright holder, and you cure the violation prior to 30 days after
        your receipt of the notice.
        
          Termination of your rights under this section does not terminate the
        licenses of parties who have received copies or rights from you under
        this License.  If your rights have been terminated and not permanently
        reinstated, you do not qualify to receive new licenses for the same
        material under section 10.
        
          9. Acceptance Not Required for Having Copies.
        
          You are not required to accept this License in order to receive or
        run a copy of the Program.  Ancillary propagation of a covered work
        occurring solely as a consequence of using peer-to-peer transmission
        to receive a copy likewise does not require acceptance.  However,
        nothing other than this License grants you permission to propagate or
        modify any covered work.  These actions infringe copyright if you do
        not accept this License.  Therefore, by modifying or propagating a
        covered work, you indicate your acceptance of this License to do so.
        
          10. Automatic Licensing of Downstream Recipients.
        
          Each time you convey a covered work, the recipient automatically
        receives a license from the original licensors, to run, modify and
        propagate that work, subject to this License.  You are not responsible
        for enforcing compliance by third parties with this License.
        
          An "entity transaction" is a transaction transferring control of an
        organization, or substantially all assets of one, or subdividing an
        organization, or merging organizations.  If propagation of a covered
        work results from an entity transaction, each party to that
        transaction who receives a copy of the work also receives whatever
        licenses to the work the party's predecessor in interest had or could
        give under the previous paragraph, plus a right to possession of the
        Corresponding Source of the work from the predecessor in interest, if
        the predecessor has it or can get it with reasonable efforts.
        
          You may not impose any further restrictions on the exercise of the
        rights granted or affirmed under this License.  For example, you may
        not impose a license fee, royalty, or other charge for exercise of
        rights granted under this License, and you may not initiate litigation
        (including a cross-claim or counterclaim in a lawsuit) alleging that
        any patent claim is infringed by making, using, selling, offering for
        sale, or importing the Program or any portion of it.
        
          11. Patents.
        
          A "contributor" is a copyright holder who authorizes use under this
        License of the Program or a work on which the Program is based.  The
        work thus licensed is called the contributor's "contributor version".
        
          A contributor's "essential patent claims" are all patent claims
        owned or controlled by the contributor, whether already acquired or
        hereafter acquired, that would be infringed by some manner, permitted
        by this License, of making, using, or selling its contributor version,
        but do not include claims that would be infringed only as a
        consequence of further modification of the contributor version.  For
        purposes of this definition, "control" includes the right to grant
        patent sublicenses in a manner consistent with the requirements of
        this License.
        
          Each contributor grants you a non-exclusive, worldwide, royalty-free
        patent license under the contributor's essential patent claims, to
        make, use, sell, offer for sale, import and otherwise run, modify and
        propagate the contents of its contributor version.
        
          In the following three paragraphs, a "patent license" is any express
        agreement or commitment, however denominated, not to enforce a patent
        (such as an express permission to practice a patent or covenant not to
        sue for patent infringement).  To "grant" such a patent license to a
        party means to make such an agreement or commitment not to enforce a
        patent against the party.
        
          If you convey a covered work, knowingly relying on a patent license,
        and the Corresponding Source of the work is not available for anyone
        to copy, free of charge and under the terms of this License, through a
        publicly available network server or other readily accessible means,
        then you must either (1) cause the Corresponding Source to be so
        available, or (2) arrange to deprive yourself of the benefit of the
        patent license for this particular work, or (3) arrange, in a manner
        consistent with the requirements of this License, to extend the patent
        license to downstream recipients.  "Knowingly relying" means you have
        actual knowledge that, but for the patent license, your conveying the
        covered work in a country, or your recipient's use of the covered work
        in a country, would infringe one or more identifiable patents in that
        country that you have reason to believe are valid.
        
          If, pursuant to or in connection with a single transaction or
        arrangement, you convey, or propagate by procuring conveyance of, a
        covered work, and grant a patent license to some of the parties
        receiving the covered work authorizing them to use, propagate, modify
        or convey a specific copy of the covered work, then the patent license
        you grant is automatically extended to all recipients of the covered
        work and works based on it.
        
          A patent license is "discriminatory" if it does not include within
        the scope of its coverage, prohibits the exercise of, or is
        conditioned on the non-exercise of one or more of the rights that are
        specifically granted under this License.  You may not convey a covered
        work if you are a party to an arrangement with a third party that is
        in the business of distributing software, under which you make payment
        to the third party based on the extent of your activity of conveying
        the work, and under which the third party grants, to any of the
        parties who would receive the covered work from you, a discriminatory
        patent license (a) in connection with copies of the covered work
        conveyed by you (or copies made from those copies), or (b) primarily
        for and in connection with specific products or compilations that
        contain the covered work, unless you entered into that arrangement,
        or that patent license was granted, prior to 28 March 2007.
        
          Nothing in this License shall be construed as excluding or limiting
        any implied license or other defenses to infringement that may
        otherwise be available to you under applicable patent law.
        
          12. No Surrender of Others' Freedom.
        
          If conditions are imposed on you (whether by court order, agreement or
        otherwise) that contradict the conditions of this License, they do not
        excuse you from the conditions of this License.  If you cannot convey a
        covered work so as to satisfy simultaneously your obligations under this
        License and any other pertinent obligations, then as a consequence you may
        not convey it at all.  For example, if you agree to terms that obligate you
        to collect a royalty for further conveying from those to whom you convey
        the Program, the only way you could satisfy both those terms and this
        License would be to refrain entirely from conveying the Program.
        
          13. Use with the GNU Affero General Public License.
        
          Notwithstanding any other provision of this License, you have
        permission to link or combine any covered work with a work licensed
        under version 3 of the GNU Affero General Public License into a single
        combined work, and to convey the resulting work.  The terms of this
        License will continue to apply to the part which is the covered work,
        but the special requirements of the GNU Affero General Public License,
        section 13, concerning interaction through a network will apply to the
        combination as such.
        
          14. Revised Versions of this License.
        
          The Free Software Foundation may publish revised and/or new versions of
        the GNU General Public License from time to time.  Such new versions will
        be similar in spirit to the present version, but may differ in detail to
        address new problems or concerns.
        
          Each version is given a distinguishing version number.  If the
        Program specifies that a certain numbered version of the GNU General
        Public License "or any later version" applies to it, you have the
        option of following the terms and conditions either of that numbered
        version or of any later version published by the Free Software
        Foundation.  If the Program does not specify a version number of the
        GNU General Public License, you may choose any version ever published
        by the Free Software Foundation.
        
          If the Program specifies that a proxy can decide which future
        versions of the GNU General Public License can be used, that proxy's
        public statement of acceptance of a version permanently authorizes you
        to choose that version for the Program.
        
          Later license versions may give you additional or different
        permissions.  However, no additional obligations are imposed on any
        author or copyright holder as a result of your choosing to follow a
        later version.
        
          15. Disclaimer of Warranty.
        
          THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
        APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
        HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
        OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
        THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
        PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
        IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
        ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
        
          16. Limitation of Liability.
        
          IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
        WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
        THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
        GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
        USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
        DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
        PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
        EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
        SUCH DAMAGES.
        
          17. Interpretation of Sections 15 and 16.
        
          If the disclaimer of warranty and limitation of liability provided
        above cannot be given local legal effect according to their terms,
        reviewing courts shall apply local law that most closely approximates
        an absolute waiver of all civil liability in connection with the
        Program, unless a warranty or assumption of liability accompanies a
        copy of the Program in return for a fee.
        
                             END OF TERMS AND CONDITIONS
        
                    How to Apply These Terms to Your New Programs
        
          If you develop a new program, and you want it to be of the greatest
        possible use to the public, the best way to achieve this is to make it
        free software which everyone can redistribute and change under these terms.
        
          To do so, attach the following notices to the program.  It is safest
        to attach them to the start of each source file to most effectively
        state the exclusion of warranty; and each file should have at least
        the "copyright" line and a pointer to where the full notice is found.
        
            <one line to give the program's name and a brief idea of what it does.>
            Copyright (C) <year>  <name of author>
        
            This program is free software: you can redistribute it and/or modify
            it under the terms of the GNU General Public License as published by
            the Free Software Foundation, either version 3 of the License, or
            (at your option) any later version.
        
            This program is distributed in the hope that it will be useful,
            but WITHOUT ANY WARRANTY; without even the implied warranty of
            MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
            GNU General Public License for more details.
        
            You should have received a copy of the GNU General Public License
            along with this program.  If not, see <https://www.gnu.org/licenses/>.
        
        Also add information on how to contact you by electronic and paper mail.
        
          If the program does terminal interaction, make it output a short
        notice like this when it starts in an interactive mode:
        
            <program>  Copyright (C) <year>  <name of author>
            This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
            This is free software, and you are welcome to redistribute it
            under certain conditions; type `show c' for details.
        
        The hypothetical commands `show w' and `show c' should show the appropriate
        parts of the General Public License.  Of course, your program's commands
        might be different; for a GUI interface, you would use an "about box".
        
          You should also get your employer (if you work as a programmer) or school,
        if any, to sign a "copyright disclaimer" for the program, if necessary.
        For more information on this, and how to apply and follow the GNU GPL, see
        <https://www.gnu.org/licenses/>.
        
          The GNU General Public License does not permit incorporating your program
        into proprietary programs.  If your program is a subroutine library, you
        may consider it more useful to permit linking proprietary applications with
        the library.  If this is what you want to do, use the GNU Lesser General
        Public License instead of this License.  But first, please read
        <https://www.gnu.org/licenses/why-not-lgpl.html>.
        
Project-URL: Homepage, https://github.com/MichaelWave369/PhiOS
Project-URL: Repository, https://github.com/MichaelWave369/PhiOS
Project-URL: Manifesto, https://enterthefield.org/phios
Keywords: phios,sovereign,local-first,shell,ai
Classifier: Development Status :: 3 - Alpha
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: GNU General Public License v3 (GPLv3)
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.11
Classifier: Topic :: Software Development :: Libraries
Classifier: Topic :: System :: Shells
Requires-Python: >=3.11
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: psutil>=5.9.0
Requires-Dist: mcp>=1.0
Provides-Extra: dev
Requires-Dist: build>=1.2.2; extra == "dev"
Requires-Dist: twine>=5.1.1; extra == "dev"
Requires-Dist: requests>=2.32.0; extra == "dev"
Requires-Dist: pytest>=8.0.0; extra == "dev"
Requires-Dist: ruff>=0.6.0; extra == "dev"
Requires-Dist: mypy>=1.11.0; extra == "dev"
Dynamic: license-file

# φ PhiOS — Sovereign Computing Shell

> “We did not come here to improve the cage. We came here to end it.”

PhiOS is the sovereign operator shell on top of PhiKernel.

Read the manifesto: https://enterthefield.org/phios  
Built by: PHI369 Labs / Parallax

Sovereign. Coherent. Local. Free.

## PhiOS on PhiKernel

Architecture relationship:

Linux  
↓  
PhiKernel = trusted runtime core (source of truth)  
↓  
PhiOS = sovereign shell / operator experience

Phase 1 integration is intentionally loose-coupled:

- PhiOS calls PhiKernel via stable CLI interfaces (`phik ... --json`).
- PhiOS re-renders operator-friendly output and composes workflows.
- PhiOS does **not** duplicate runtime internals.

PhiKernel remains authoritative for:

- anchor
- capsules
- heart
- coherence
- routing safety

## Install

```bash
python -m pip install -r requirements.txt
python -m pip install -e .
```

## Verify toolchain

```bash
phi --help
phik --help
phik status --json
```

## Quick start

```bash
phi
phi status
phi coherence
phi ask "How should I begin?"
phi sovereign export ./phi_snapshot.json
```


## MCP interface (Phase 1 + Phase 2)

PhiOS exposes an MCP interface layer over existing PhiOS/PhiKernel capabilities.
This is additive interface work only; it does not replace runtime internals.
**PhiKernel remains source of truth** for status, field, anchor, capsules, and pulse behavior.

Run the stdio MCP server:

```bash
phi-mcp
```

Resources:
- `phios://field/state`
- `phios://coherence/lt`
- `phios://cognition/recommendation`
- `phios://system/status`
- `phios://mcp/discovery`
- `phios://history/recent_capsules`
- `phios://history/recent_sessions`
- `phios://history/recent_field_snapshots`
- `phios://observatory/index`
- `phios://observatory/dashboard`
- `phios://observatory/atlas_gallery`
- `phios://observatory/storyboards/recent`
- `phios://observatory/dossiers/recent`
- `phios://observatory/field_libraries/recent`
- `phios://observatory/study_halls/index`
- `phios://observatory/reading_rooms/index`
- `phios://observatory/shelves/index`
- `phios://observatory/field_libraries/index`
- `phios://observatory/dossiers/index`
- `phios://observatory/storyboards/index`
- `phios://archive/journey_ensembles/index`
- `phios://browse/libraries`
- `phios://browse/learning_paths`
- `phios://browse/collections`
- `phios://browse/programs`
- `phios://browse/comparative`
- `phios://collections/field_libraries/rollup`
- `phios://collections/shelves/rollup`
- `phios://collections/reading_rooms/rollup`
- `phios://collections/study_halls/rollup`
- `phios://collections/curricula/rollup`
- `phios://collections/journey_ensembles/rollup`
- `phios://programs/curricula/rollup`
- `phios://programs/study_halls/rollup`
- `phios://programs/thematic_pathways/rollup`
- `phios://programs/syllabi/rollup`
- `phios://programs/journey_ensembles/rollup`
- `phios://browse/curricula`
- `phios://browse/cohorts`
- `phios://browse/learning_tracks`
- `phios://capstones/syllabi/rollup`
- `phios://capstones/atlas_cohorts/rollup`
- `phios://capstones/field_libraries/rollup_family`
- `phios://capstones/dossiers/rollup_family`
- `phios://capstones/storyboards/rollup_family`
- `phios://browse/capstones`
- `phios://browse/collections_family`
- `phios://browse/learning_programs`
- `phios://browse/comparative_learning`
- `phios://browse/study_tracks`
- `phios://catalogs/learning`
- `phios://catalogs/capstones`
- `phios://catalogs/programs`
- `phios://catalogs/collections`
- `phios://maps/learning`
- `phios://maps/capstones`
- `phios://maps/programs`
- `phios://maps/collections`
- `phios://dashboards/discovery`
- `phios://dashboards/archive`
- `phios://dashboards/learning`
- `phios://dashboards/capstones`
- `phios://families/overview`
- `phios://families/learning`
- `phios://families/capstones`
- `phios://families/dashboard_overview`
- `phios://families/dashboard_learning`
- `phios://families/dashboard_capstones`
- `phios://consoles/navigation`
- `phios://consoles/archive`
- `phios://consoles/learning`
- `phios://consoles/capstones`
- `phios://browse/observatory_families`
- `phios://browse/learning_families`
- `phios://browse/collection_families`
- `phios://browse/capstone_families`
- `phios://browse/archive_families`
- `phios://browse/archive_groups`
- `phios://browse/learning_maps`
- `phios://browse/cross_catalog`
- `phios://browse/program_families`
- `phios://browse/learning`
- `phios://browse/archive`
- `phios://browse/sessions`
- `phios://browse/observatory`
- `phios://browse/recent`
- `phios://browse/overview`
- `phios://archive/curricula/index`
- `phios://archive/longitudinal/index`
- `phios://archive/route_compares/index`
- `phios://archive/atlas/index`
- `phios://archive/pathways/index`
- `phios://sessions/recent_reports`
- `phios://sessions/recent_checkins`
- `phios://sessions/current`
- `phios://agents/active`
- `phios://agents/{run_id}`
- `phios://agents/{run_id}/events`
- `phios://agents/memory/{topic}`
- `phios://agents/memory/{topic}/coherence`
- `phios://agents/deliberations/recent`
- `phios://debates/recent`
- `phios://debates/{session_id}`
- `phios://reviews/recent`
- `phios://reviews/{panel_id}`
- `phios://cognition/atoms`
- `phios://figures/fitness`
- `phios://figures/fitness/{figure}`
- `phios://figures/recommendation/{task_key}`
- `phios://dispatch/graph/last`

Tools:
- `phi_status`
- `phi_ask`
- `phi_recommend_cognitive_arch`
- `phi_pulse_once`
- `phi_observatory_summary`
- `phi_recent_activity`
- `phi_library_summary`
- `phi_storyboard_summary`
- `phi_atlas_summary`
- `phi_discovery`
- `phi_discovery_dashboard_summary`
- `phi_navigation_console_summary`
- `phi_browse_observatory`
- `phi_archive_summary`
- `phi_session_summary`
- `phi_collection_summary`
- `phi_program_summary`
- `phi_curation_summary`
- `phi_capstone_summary`
- `phi_catalog_summary`
- `phi_learning_map_summary`
- `phi_dispatch_agents`
- `phi_list_agents`
- `phi_agent_status`
- `phi_kill_agent`
- `phi_store_deliberation`
- `phi_debate_coherence_gate`
- `phi_review_coherence_gate`
- `phi_recommend_cognitive_atoms`
- `phi_record_figure_outcome`
- `phi_figure_fitness_report`
- `phi_recommend_figure_for_task`
- `phi_optimize_dispatch_graph`

Prompt:
- `field_guidance`

Phase 2 additions:
- Schema versioning on MCP payloads via top-level `schema_version` plus `resource_version`/`tool_version` where applicable.
- Default-safe pulse capability gating for `phi_pulse_once`; enable explicitly with `PHIOS_MCP_ALLOW_PULSE=true`.
- Read-only history resources from grounded local/adapter data with sensible recent limits.

Phase 3 additions:
- Richer read-only observatory resources for dashboard/gallery/storyboard/dossier/field-library discovery and summaries.
- Observatory resources are additive interface surfaces for local observatory artifacts; they are non-truth-bearing and do not replace PhiKernel truth logic.

Phase 4 additions:
- Optional lightweight capability scopes via `PHIOS_MCP_CAPABILITIES` (for example: `read_state,read_history,read_observatory,prompt_guidance,pulse_once,agent_dispatch,agent_kill,agent_memory_write`).
- New read-safe summary tools: `phi_observatory_summary`, `phi_recent_activity`, and `phi_library_summary`.
- Capability gating remains local/lightweight for now (not a full identity/auth platform).

Phase 5 additions:
- Client-facing discovery surfaces: `phios://mcp/discovery` and `phi_discovery` (registry + capability/policy posture).
- Additional bounded summary tools: `phi_storyboard_summary` and `phi_atlas_summary`.
- Real-client harness prep tests included; full SDK-client handshake assertions run only when MCP client runtime modules are available in CI/runtime.

Phase 6 additions:
- Optional lightweight client profile presets via `PHIOS_MCP_PROFILE` (`read_only`, `observer`, `operator`, `developer`) resolved into capability scopes.
- New read-only observatory browsing resources for index-style navigation (storyboards, dossiers, field libraries, shelves, reading rooms, study halls).
- New bounded browse tool: `phi_browse_observatory` synthesizing index surfaces for ergonomic client browsing.
- Discovery payloads now include profile and resolved capability posture details (`profile`, `resolved_capabilities`, `resource_counts`, `tool_counts`, `prompt_counts`).

Phase 7 additions:
- Session-oriented read resources: `phios://sessions/current`, `phios://sessions/recent_checkins`, `phios://sessions/recent_reports`.
- Richer archive browsing resources for pathways/atlas/route-compares/longitudinal/curricula/journey-ensembles.
- New read-safe synthesis tools: `phi_session_summary` and `phi_archive_summary`.
- Deeper runtime-gated client integration prep coverage for session/archive discovery→resource→tool paths where SDK runtime is available.

Phase 8 additions:
- Stable deterministic browse presets (`overview`, `recent`, `observatory`, `sessions`, `archive`, `learning`, `libraries`) exposed in discovery metadata and read-only browse resources.
- Richer archive navigation rollups in `phi_archive_summary` and grouped discovery fields (`browse_presets`, `resource_groups`, `tool_groups`, `archive_rollups`).
- Preset-aware browse/summary parameters for deterministic client browsing (`preset`, `artifact_family`, `limit`, `include_counts`, `include_rollups`).
- Deeper runtime-gated client integration prep notes for discovery → preset browse → resource read → tool invoke flows when SDK runtime is available.

Phase 9 additions:
- Stable collection/library rollup resources for `field_libraries`, `shelves`, `reading_rooms`, `study_halls`, `curricula`, and `journey_ensembles` under `phios://collections/*/rollup`.
- Richer learning-oriented browse presets/resources (`learning_paths`, `collections`, `programs`, `comparative`) with deterministic payload structure and grounded local data only.
- New bounded synthesis tool `phi_collection_summary` for collection/library rollup aggregation with schema markers and generated timestamps.
- Discovery now includes collection and learning coverage metadata (`collection_rollups`, `learning_presets`, `collection_groups`, `browse_surface_counts`) for easier client navigation.
- Runtime-gated Phase 9 client-path test hook added for discovery → preset browse → rollup read → archive read → tool invoke flow expansion when SDK runtime allows.

Phase 10 additions:
- Stable program/learning rollup resources under `phios://programs/*/rollup` for curricula, study halls, thematic pathways, syllabi, and journey ensembles.
- New deterministic program-level browse presets/resources (`curricula`, `cohorts`, `learning_tracks`) exposed through the existing browse preset surface.
- New bounded read-only summary tools `phi_program_summary` and `phi_curation_summary` for grounded program/collection synthesis without speculative recommendations.
- Discovery now includes program coverage metadata (`program_rollups`, `learning_groups`, `program_surface_counts`) in addition to existing profile/capability posture fields.
- Runtime-gated Phase 10 client-path test hook added for discovery → browse preset → collection rollup → program rollup → summary tool invoke flow expansion when SDK runtime allows.


Phase 16 additions (Issue #79 experimental AgentCeption conductor):
- New shell orchestration commands: `phi dispatch "<task>"` and `phi agents [list|status|kill|log]`.
- New MCP tools for dispatch lifecycle orchestration: `phi_dispatch_agents`, `phi_list_agents`, `phi_agent_status`, `phi_kill_agent`.
- New read-only MCP resources for active runs and run traces: `phios://agents/active`, `phios://agents/{run_id}`, `phios://agents/{run_id}/events`.
- Dispatch/kill actions are explicitly capability gated (`agent_dispatch`, `agent_kill`) with structured deny payloads.
- Integration remains additive/experimental: PhiOS is shell + observatory orchestrator, PhiKernel remains runtime truth source, and AgentCeption is treated as an external planning/dispatch engine.
- Scientific framing remains explicit: C* is theoretical, bio-vacuum targets are experimental, and Hunter's C is unconfirmed.
- Environment toggles for integration:
  - `PHIOS_AGENTCEPTION_ENABLED=true|false`
  - `PHIOS_AGENTCEPTION_BASE_URL=http://127.0.0.1:8787`
  - optional `PHIOS_AGENTCEPTION_TOKEN`


Phase 17 additions (Issue #76 field-guided cognitive architecture selection):
- New read-only advisory shell command: `phi recommend-arch` (or `phi recommend-arch --json`).
- New MCP read-only advisory tool: `phi_recommend_cognitive_arch`.
- New MCP read-only resource: `phios://cognition/recommendation`.
- Recommendation output is deterministic and explainable (`figure`, `archetype`, `reason`, `confidence`, signals, candidate scores).
- This recommendation is an additive experimental prior for orchestration only, not a PhiKernel truth mutation.
- Scientific framing remains explicit: `C*` is theoretical, bio-vacuum target is experimental, and Hunter's C remains unconfirmed.
- AgentCeption interoperability notes (opt-in on AgentCeption side):
  - `AC_PHIOS_ENDPOINT`
  - `AC_PHIOS_FIELD_WEIGHT`

Phase 18 additions (Issue #77 observatory-backed agent long-term memory):
- New read-only MCP memory resources:
  - `phios://agents/memory/{topic}`
  - `phios://agents/memory/{topic}/coherence`
  - `phios://agents/deliberations/recent`
- New MCP write-like tool (capability-gated): `phi_store_deliberation`.
- New shell memory read/write surfaces:
  - `phi memory topic <topic>`
  - `phi memory coherence <topic>`
  - `phi memory recent`
  - `phi memory store <topic> ... --yes` (gated)
- Storage model is local-first and observatory-backed via narrative artifacts (`~/.phios/journal/visual_bloom/narratives/agent_memory_<topic>.json`) with additive `agent_deliberations` entries.
- This is additive experimental archive memory, not a truth-layer mutation; PhiKernel remains source of truth.

Phase 19 additions (Issue #75 cognitive debate arena coherence gate):
- New MCP debate gate tool: `phi_debate_coherence_gate(session_id, round, positions, threshold, persist)`.
- New read-only MCP debate resources:
  - `phios://debates/recent`
  - `phios://debates/{session_id}`
- New shell command:
  - `phi debate gate --session-id <id> --round <n> --positions <json> [--threshold <float>] [--persist] [--json]`
- Convergence model:
  - `converged` when current coherence crosses threshold (default near `C*_theoretical`)
  - `deadlock` when coherence remains below threshold with low recent trace span after multiple rounds
  - otherwise `continue`
- Optional additive observatory persistence (`--persist` / tool `persist=true`) stores debate outcome, dissent, and coherence trace in agent memory narratives.
- This remains additive/experimental and non-truth-bearing; PhiKernel remains source of truth.

Phase 20 additions (Issue #78 adversarial architecture review coherence gate):
- New MCP tool: `phi_review_coherence_gate(round, reviewer_grades, reviewer_critiques, pr_number, panel_id, mediator_summary, persist)`.
- New read-only MCP resources:
  - `phios://reviews/recent`
  - `phios://reviews/{panel_id}`
- New shell command:
  - `phi review gate --round <n> --reviewer-grades <json> --reviewer-critiques <json> [--panel-id <id>] [--pr-number <n>] [--mediator-summary <text>] [--persist] [--json]`
- Deterministic gate semantics:
  - `converged` when coherence is strong and grade spread is narrow
  - `mediate` when disagreement/critique pressure remains high (or coherence plateaus with unresolved spread)
  - `continue` otherwise
- Optional persistence (`persist`) writes additive review outcomes/dissent/coherence traces into existing observatory-backed agent-memory narratives.
- This is additive and experimental; PhiKernel remains source of truth and coherence is used as an oracle signal only.

Phase 21 additions (Issue #81 sector-to-atom cognitive overrides):
- New read-only shell command: `phi recommend-atoms` (or `phi recommend-atoms --json`).
- New MCP read-only tool: `phi_recommend_cognitive_atoms`.
- New MCP read-only resource: `phios://cognition/atoms`.
- Deterministic sector-to-atom mapping rules convert sector signals into atom overrides:
  - `geometry_balance` -> `epistemic_style`
  - `vacuum_proximity` -> `creativity_level`
  - `observer_entropy` -> `uncertainty_handling` and `error_posture`
  - `collector_activity` -> `cognitive_rhythm`
  - `mirror_alignment` -> `collaboration_posture`
  - `emotion_field` -> `communication_style`
- Optional additive integration: the Issue #76 cognitive-architecture tool/resource now include `atom_recommendation` metadata.
- This remains additive, read-only, experimental, and advisory; PhiKernel remains source of truth.

Phase 22 additions (Issue #80 living cognitive ecosystem figure fitness):
- New shell figure fitness commands:
  - `phi agents figures`
  - `phi agents figures --top <n>`
  - `phi agents figures --sector <sector>`
  - `phi agents evolve [--top <n>] [--sector <sector>] [--task-key <key>] [--skill <skill>] [--min-coherence <v>]`
- New MCP tools:
  - `phi_record_figure_outcome` (capability-gated write)
  - `phi_figure_fitness_report` (read-only)
  - `phi_recommend_figure_for_task` (read-only)
- New read-only MCP resources:
  - `phios://figures/fitness`
  - `phios://figures/fitness/{figure}`
  - `phios://figures/recommendation/{task_key}`
- `phios://dispatch/graph/last`
- Storage model is local-first and inspectable under `~/.phios/journal/visual_bloom/narratives/figure_fitness_records.json` with append-only-like `figure_outcomes` entries.
- Deterministic report metrics include `grade_success_rate`, `avg_merge_time_minutes`, `avg_coherence`, `redispatch_rate`, and `close_rate`.
- This remains additive and experimental; write path is explicitly capability-gated (`figure_fitness_write`), and recommendations are advisory only.

Phase 23 additions (Issue #82 golden lattice dependency navigator):
- New deterministic dispatch-graph optimizer service: `phios/services/dispatch_graph.py`.
- New shell command:
  - `phi dispatch optimize --graph <json> [--json]`
- New MCP read-only tool:
  - `phi_optimize_dispatch_graph`
- New read-only MCP resource:
  - `phios://dispatch/graph/last`
- Graph model supports node fields such as: `id`, `label`, `dependencies`, `estimated_cost`, `sector`, `skills`, `figure`, `atom_overrides`, and `priority`.
- Deterministic optimization rules:
  - dependency correctness via topological ordering first
  - ready-node ranking by depth(desc), priority(desc), estimated_cost(asc), id(asc)
  - parallel wave construction for dependency-safe batching
  - bottleneck detection by fan-out
- The optimizer remains additive, experimental, and advisory; no autonomous execution.

Phase 11 additions:
- Stable capstone/collection-family rollups under `phios://capstones/*` for syllabi, atlas cohorts, field-library families, dossier families, and storyboard families.
- Richer deterministic learning browse families (`capstones`, `collections_family`, `learning_programs`, `comparative_learning`, `study_tracks`) via stable browse preset surfaces.
- New bounded read-only synthesis tool `phi_capstone_summary` for capstone/family rollup aggregation grounded in local metadata only.
- Discovery now includes capstone/family visibility and counts (`capstone_rollups`, `collection_family_rollups`, `learning_browse_families`, `capstone_surface_counts`).
- Broader runtime-gated Phase 11 client-path hook added for discovery → browse preset → rollup reads → summary invocation flow expansion when SDK runtime allows.

Phase 12 additions:
- Stable archive-wide catalog resources for learning/capstones/programs/collections under `phios://catalogs/*` with deterministic read-only schema-marked payloads.
- Richer observatory-family and learning-family browse groups (`observatory_families`, `learning_families`, `collection_families`, `capstone_families`, `archive_families`) via browse preset resources.
- New bounded read-only summary tool `phi_catalog_summary` for catalog synthesis grounded only in local catalog metadata.
- Discovery now includes catalog/family visibility fields (`catalog_resources`, `observatory_family_groups`, `catalog_surface_counts`, `browse_family_groups`).
- Broader runtime-gated Phase 12 client-path hook added for discovery → family browse → catalog/rollup reads → summary invocation flow expansion when SDK runtime allows.

Phase 13 additions:
- Stable cross-catalog learning map resources under `phios://maps/*` (`learning`, `capstones`, `programs`, `collections`) with deterministic metadata-driven relationships and schema markers.
- Learning-map payloads expose grounded availability and family metadata (`generated_at`, `count`, `families`, `linked_catalogs`, `family_counts`, `tag_coverage`, `artifact_family_counts`, `dominant_sector_counts`, `route_available`, `longitudinal_available`, `diagnostics_available`) with graceful sparse/no-data defaults.
- Richer archive-family discovery and browse surfaces via additional grouped browse presets/resources (`archive_groups`, `learning_maps`, `cross_catalog`, `program_families`).
- New bounded read-only summary tool `phi_learning_map_summary` for cross-catalog map synthesis grounded strictly in local metadata; `phi_catalog_summary` also supports optional additive `include_map_counts`.
- Discovery now includes cross-catalog/learning-map visibility (`learning_maps`, `archive_family_groups`, `cross_catalog_groups`, `map_surface_counts`) plus grouped counts for easier deterministic client routing.
- Broader runtime-gated Phase 13 client-path hook added for discovery → family browse → rollup/catalog/map reads → session/archive reads → bounded summary flow expansion when SDK runtime allows.
- All map/browse/summary surfaces are additive and non-truth-bearing; PhiKernel remains source of truth.


Phase 14 additions:
- Stable archive-wide dashboard resources under `phios://dashboards/*` (`discovery`, `archive`, `learning`, `capstones`) with deterministic read-only metadata summaries.
- Stable family navigation resources under `phios://families/*` (`overview`, `learning`, `capstones`) for cross-surface relationship orientation across collections/programs/capstones/catalogs/maps.
- New bounded read-only synthesis tool `phi_discovery_dashboard_summary` for dashboard/family synthesis from existing MCP metadata only.
- Discovery now includes dashboard/family visibility fields (`dashboard_resources`, `family_resources`, `family_navigation_groups`, `dashboard_surface_counts`) for easier client routing.
- Runtime-gated SDK-backed client harness coverage is expanded toward discovery → family browse → rollup → catalog → map → dashboard → session/archive → bounded summary flow, with pulse deny posture assertions where runtime support is available.
- All dashboard/browse/summary surfaces remain additive and non-truth-bearing; PhiKernel remains source of truth.


Phase 15 additions:
- Stable archive-wide navigation console resources under `phios://consoles/*` (`navigation`, `archive`, `learning`, `capstones`) with deterministic read-only metadata summaries over existing dashboards/families/maps.
- Richer family dashboard summary resources under `phios://families/*` (`dashboard_overview`, `dashboard_learning`, `dashboard_capstones`) to clarify relationships across families, catalogs, maps, and dashboards.
- New bounded read-only synthesis tool `phi_navigation_console_summary` for console-level client routing summaries grounded only in existing MCP metadata/resources.
- Additive enhancements to `phi_discovery_dashboard_summary` with optional `family_dashboard` and `include_family_dashboard_counts` arguments.
- Discovery now includes Phase 15 console/family-dashboard visibility (`console_resources`, `family_dashboard_resources`, `console_surface_counts`, `family_dashboard_counts`) for clearer deterministic client routing.
- Runtime-gated SDK-backed client harness coverage is expanded toward discovery → family browse → rollup → catalog → map → dashboard → console → session/archive → bounded summary flow, with pulse deny posture assertions where runtime support is available.
- All console/dashboard/summary surfaces remain additive and non-truth-bearing; PhiKernel remains source of truth.

Framing discipline is preserved in MCP outputs and prompts:
- `C*` is treated as theoretical.
- bio-vacuum targets are experimental.
- Hunter's C remains unconfirmed.

## First Day with PhiOS

```bash
phi doctor
phi init --passphrase "change-me" --sovereign-name "Tal-Aren-Vox" --user-label "Ori"
phi pulse once
phi status
phi coherence
phi ask "How should I begin?"
```

## Command reference (v0.3)

- `phi help`
- `phi version`
- `phi doctor [--json]`
- `phi init --passphrase <value> --sovereign-name <name> --user-label <label> [--resonant-label <label>] [--json]`
- `phi pulse once [--checkpoint <path>] [--passphrase <value>] [--json]`
- `phi observatory [--json]`
- `phi observatory export <path.json>`
- `phi z map [--json]`
- `phi mind [--json]`
- `phi mind map [--json]`
- `phi mind export <path.json>`
- `phi session start [--json]`
- `phi session checkin [--json]`
- `phi session export <path.json>`
- `phi bio list [--json]`
- `phi bio add --name <name> --compound <compound> --source <source> [--dose <dose>] [--unit <unit>] [--timing <timing>] [--notes <notes>] [--json]`
- `phi bio show [--json]`
- `phi bio export <path.json>`
- `phi view --mode sonic`
- `phi view --mode sonic --live --refresh-seconds 2 --duration 60`
- `phi view --mode sonic --journal --label morning`
- `phi view --mode sonic --live --journal --label focus`
- `phi view --mode sonic --replay <session_id>`
- `phi view --mode sonic --preset stable --lens ritual`
- `phi view --mode sonic --live --preset diagnostic --audio-reactive`
- `phi view --mode sonic --journal --collection morning`
- `phi view --browse-collections`
- `phi view --browse-collection morning`
- `phi view --compare <session_a[:state_idx]> <session_b[:state_idx]>`
- `phi view --mode sonic --replay <session_id> --state-idx <n>`
- `phi view --mode sonic --replay <session_id> --next-state`
- `phi view --mode sonic --replay <session_id> --prev-state`
- `phi view --mode sonic --compare <left> <right> --export-report <path.json>`
- `phi status [--json]`
- `phi coherence [--json]`
- `phi coherence live`
- `phi ask <prompt> [--json]`
- `phi sovereign export <path.json>`
- `phi sovereign verify <path>`
- `phi sovereign compare <path_a> <path_b>`
- `phi sovereign annotate <path> <note>`
- `phi brainc status`
- `phi tbrc status`
- `phi memory [status|search <query>|recent]`
- `phi archive [timeline|add|export]`
- `phi kg [stats|search <concept>]`
- `phi sync [status|push|pull|both]`


## Hemavit Observatory

PhiOS can interpret PhiKernel runtime state through a Hemavit / TIEKAT observatory lens.
This layer is symbolic interpretation and operator workflow composition.
It does **not** replace PhiKernel's coherence engine or runtime source-of-truth.

```bash
phi observatory
phi z map
phi observatory export ./phi_observatory_snapshot.json
```


## Ψ_mind Observatory

PhiOS can interpret PhiKernel runtime state through a `Ψ_mind` observatory lens.
This layer is symbolic interpretation and operator workflow composition.
It does **not** replace PhiKernel's coherence engine or runtime source-of-truth.

```bash
phi mind
phi mind map
phi mind export ./phi_mind_snapshot.json
```


## Session Layer

PhiOS Session Layer is a composition surface across runtime + observatory + mind views.
It unifies startup and daily check-in workflows while keeping PhiKernel as source-of-truth.

It uses symbolic interpretation terms for operator check-ins, including:
- `observer_state`
- `self_alignment`
- `information_density` (`G_info(I)`)
- `entropy_load` (`η S_ent`)
- `emergence_pressure` (`T_emerge`)

```bash
phi session start
phi session checkin
phi session export ./phi_session_snapshot.json
```


## Bioeffector Layer

PhiOS can track compounds / extracts / herbal supports as part of operator workflow.
This is a local workflow and observatory layer for session correlation, not substrate truth.
It does **not** replace PhiKernel runtime truth and does **not** constitute medical advice.

```bash
phi bio add --name "Lion's Mane" --compound "Erinacine A" --source "mycelium" --dose 500 --unit mg --timing morning
phi bio list
phi bio show
phi bio export ./phi_bio_snapshot.json
```


## Visual Bloom Adapter

PhiOS can render a local visual bloom snapshot from live PhiKernel telemetry.
This is an operator-facing visual lens and composition layer, not a second runtime engine.

```bash
phi view --mode sonic
phi view --mode sonic --live
phi view --mode sonic --live --refresh-seconds 1.5 --duration 120
phi view --mode sonic --journal --label morning
phi view --mode sonic --live --journal --label focus
phi view --mode sonic --replay 20260101T120000Z_123456
phi view --mode sonic --preset stable --lens ritual
phi view --mode sonic --live --preset diagnostic --audio-reactive
phi view --mode sonic --journal --collection morning
phi view --browse-collections
phi view --browse-collection morning
phi view --compare 20260101T120000Z_123456:0 20260102T073000Z_654321:0
phi view --mode sonic --replay 20260101T120000Z_123456 --state-idx 3
phi view --mode sonic --replay 20260101T120000Z_123456 --next-state
phi view --mode sonic --compare 20260101T120000Z_123456:0 20260102T073000Z_654321:0 --export-report ./phi_compare_report.json
phi view --gallery
phi view --gallery --collection morning
phi view --mode sonic --compare 20260101T120000Z_123456:0 20260102T073000Z_654321:0 --save-compare morning_pair
phi view --browse-compares
phi view --mode sonic --load-compare morning_pair
phi view --mode sonic --compare 20260101T120000Z_123456:0 20260102T073000Z_654321:0 --export-bundle ./exports/morning_pair_bundle
phi view --gallery --search morning --filter-mode live --filter-preset stable
phi view --mode sonic --compare 20260101T120000Z_123456:0 20260102T073000Z_654321:0 --export-bundle ./exports/morning_pair_bundle --with-integrity --bundle-label morning_pair
phi view --create-narrative morning_story --narrative-title "Morning Story" --narrative-summary "Operator shift arc"
phi view --add-to-narrative morning_story --session 20260101T120000Z_123456:0 --entry-note "Initial field posture"
phi view --add-to-narrative morning_story --compare 20260101T120000Z_123456:0 20260102T073000Z_654321:0 --entry-note "Stability delta"
phi view --browse-narratives
phi view --load-narrative morning_story
phi view --export-atlas morning_story ./exports/morning_story_atlas --with-integrity
phi view --create-constellation sky_map --constellation-title "Sky Map" --constellation-summary "Cross-shift threads" --tags coherence,bridge
phi view --add-to-constellation sky_map --narrative morning_story --entry-note "Primary arc" --tags anchor
phi view --add-to-constellation sky_map --compare-set morning_pair --entry-note "Key delta"
phi view --browse-constellations
phi view --load-constellation sky_map
phi view --export-constellation sky_map ./exports/sky_map --with-integrity
phi view --link-narrative morning_story --link-type narrative --target-ref evening_story --entry-note "continuation" --tags bridge
phi view --create-pathway shift_journey --pathway-title "Shift Journey" --pathway-summary "Guided arc" --tags coherence,experimental
phi view --add-to-pathway shift_journey --session 20260101T120000Z_123456:0 --step-note "Entry baseline"
phi view --add-to-pathway shift_journey --narrative morning_story --step-note "Narrative anchor"
phi view --add-to-pathway shift_journey --atlas ./exports/morning_story_atlas --step-note "Atlas handoff"
phi view --add-to-pathway shift_journey --constellation sky_map --step-note "Cross-link context"
phi view --browse-pathways
phi view --load-pathway shift_journey
phi view --export-pathway shift_journey ./exports/shift_journey --with-integrity
phi view --search coherence --search-tags coherence --search-type pathway --search-bio experimental
```

Snapshot mode generates a one-shot artifact from current PhiKernel state.
Live mode writes the HTML artifact once, then updates a local JSON params file on interval while the page performs in-place polling (no full page reload).

Optional journaling writes reproducible visual-state archives under `~/.phios/journal/visual_bloom/<session_id>/` with `session.json` and `latest.params.json`. Replay mode renders a saved state locally without polling PhiKernel.

Phase 5 adds optional preset packs and named visual lenses (`stable`, `ritual`, `diagnostic`, `bloom`) that shape rendering interpretation deterministically without changing kernel truth.

Phase 6 adds named archive collections and local browse/compare workflows. You can tag sessions with `--collection`, browse collections/sessions from disk, and compare two saved states side-by-side without polling PhiKernel.

Phase 7 adds replay state stepping (`--state-idx`, `--next-state`, `--prev-state`), concise compare diff metrics, and optional JSON report export via `--export-report` for local observatory comparisons.

Phase 8 adds a static archive gallery (`--gallery`), saved compare sets (`--save-compare`, `--browse-compares`, `--load-compare`), and portable observatory compare bundles (`--export-bundle`).

Phase 9 adds richer gallery filtering/search (`--search`, `--filter-mode`, `--filter-preset`, `--filter-lens`, `--filter-audio`, `--filter-label`, `--filter-session`), preview metadata on sessions/bundles, and optional bundle integrity metadata (`--with-integrity`, `--bundle-label`).

Phase 10 adds curated narratives/storyboards and portable Field Atlas export (`--create-narrative`, `--add-to-narrative`, `--browse-narratives`, `--load-narrative`, `--export-atlas`) so saved sessions/compares can be assembled into ordered observatory arcs.

Phase 11 adds thematic tags (`--tags`), cross-narrative links (`--link-narrative`, `--link-type`, `--target-ref`), and constellation maps (`--create-constellation`, `--add-to-constellation`, `--browse-constellations`, `--load-constellation`, `--export-constellation`) for multi-artifact curation.

Phase 12 adds curated operator pathways/journeys (`--create-pathway`, `--add-to-pathway`, `--browse-pathways`, `--load-pathway`, `--export-pathway`) and local metadata search (`--search`, `--search-tags`, `--search-type`, `--search-bio`) across sessions/compares/narratives/atlases/constellations/pathways.


### Experimental bio-resonance framing (careful distinction)

PhiOS uses **explicitly experimental** bio-resonance metadata for operator interpretation only:

- `C_STAR_THEORETICAL = φ / 2 ≈ 0.809016994...`
- `BIO_VACUUM_TARGET = 0.81055`
- `BIO_VACUUM_BAND_LOW = 0.807`
- `BIO_VACUUM_BAND_HIGH = 0.813`
- `BIO_VACUUM_STATUS = "experimental"`
- `HUNTER_C_STATUS = "unconfirmed"`
- `BIO_MODEL_PROVENANCE = "proxy-calibrated, not empirically confirmed"`

Important: PhiOS does **not** present `BIO_VACUUM_TARGET` as a proven physical constant or as validated Hunter's C. This layer is optional, additive, and used for cautious operator-side annotation/search/journey guidance.

Audio-reactive coupling is optional and off by default (`--audio-reactive`). If local audio support is unavailable, PhiOS continues gracefully without audio modulation.

State references support optional indexing syntax (`<session_id>:<state_idx>`). If omitted, replay/compare defaults to the latest state. Older archives without new metadata fields still replay/compare with safe defaults.

Compare bundle manifest (`bundle_manifest.json`) uses a stable schema with: `bundle_version`, `manifest_version`, `bundle_type`, `bundle_label`, `bundle_created_at`, `source_refs`, `included_files`, `integrity_mode`, optional `file_hashes_sha256`, `report_schema_version`, `compatibility_version`, and `compatibility_notes`.

Field Atlas manifest (`atlas_manifest.json`) includes: `atlas_version`, `manifest_version`, `atlas_type`, `narrative_name`, `bundle_created_at`, `entry_count`, `included_files`, `integrity_mode`, optional `file_hashes_sha256`, `preview`, `compatibility_version`, and `compatibility_notes`.

Constellation manifest (`constellation_manifest.json`) includes: `constellation_version`, `manifest_version`, `constellation_type`, `constellation_name`, `bundle_created_at`, `entry_count`, `link_count`, `tags`, `included_files`, `integrity_mode`, optional `file_hashes_sha256`, `preview`, `compatibility_version`, and `compatibility_notes`.

Pathway manifest (`pathway_manifest.json`) includes: `pathway_version`, `manifest_version`, `pathway_type`, `pathway_name`, `bundle_created_at`, `step_count`, `tags`, `bio_context`, `included_files`, `integrity_mode`, optional `file_hashes_sha256`, `preview`, `compatibility_version`, and `compatibility_notes`.

The adapter reads PhiKernel field_state, maps it into visual parameters, renders a local HTML artifact,
and opens it in the default browser.

## Security posture

- Local-first by default.
- Unknown command passthrough executes without `shell=True` to reduce injection risk.
- PhiKernel adapter commands execute with `shell=False` and strict JSON parsing.
- Sovereign export validates output path shape (`.json`, no `..` traversal segments).
- No runtime tracking code and no mandatory cloud dependencies.


## Phase 13: Branching Journeys, Recommendations, and Golden Kernels

Phase 13 adds additive local curation surfaces while preserving existing snapshot/live/replay/compare/gallery/bundle/narrative/atlas/constellation/pathway flows.

### Exact theoretical and experimental framing

- `PHI = (1 + sqrt(5)) / 2`
- `C_STAR_THEORETICAL = PHI / 2 = (1 + sqrt(5)) / 4`
- Symbolic equivalence (documentational): `C_STAR_THEORETICAL = cos(36°) = sin(54°)`
- `BIO_VACUUM_TARGET = 0.81055`
- `BIO_VACUUM_BAND_LOW = 0.807`
- `BIO_VACUUM_BAND_HIGH = 0.813`
- `BIO_VACUUM_STATUS = "experimental"`
- `HUNTER_C_STATUS = "unconfirmed"`
- `BIO_MODEL_PROVENANCE = "proxy-calibrated, not empirically confirmed"`

This repository treats the bio target and golden kernels as optional experimental operator tooling, not empirical proof and not runtime source-of-truth logic.

### Experimental golden kernels

`phios.ml.golden_kernels` includes:

- `golden_rbf(...)`
- `golden_angular_rbf(...)`
- `golden_periodic(...)`
- `golden_target_angle_score(...)`

These are used only for local similarity/recommendation hints. They are not a claim of universal kernel optimality.

### New CLI additions

- `phi view --link-pathway-step <pathway> --from-step <id> --to-step <id> --branch-label <label>`
- `phi view --recommend-for <ref>`
- `phi view --dashboard [--output <path.html>] [--search <query>]`

### Backward compatibility

All new branching/recommendation/dashboard/golden-kernel data is additive. Older artifacts without tags, preview metadata, integrity metadata, bio metadata, or branching metadata continue to load with safe defaults.


## Phase 14: Golden Lattice, Adaptive Affinity, and Strategy Benchmarks

Phase 14 extends local recommendation tooling with an **experimental** 4D golden-lattice layer and adaptive local affinity scoring. These additions are optional and are not used for PhiKernel core truth logic.

### New experimental ML modules

- `phios.ml.golden_lattice`:
  - `build_lattice_4d_nodes(...)`
  - `golden_lattice_kernel_l1(...)`
  - `golden_lattice_sparse_graph(...)`
  - `golden_lattice_resonance_score(...)`
  - `estimate_local_scales(...)`
  - `adaptive_golden_affinity(...)`
  - `update_memory_weights(...)`
- `phios.ml.benchmark_recommendations`:
  - local exploratory strategy comparison and JSON summary helpers.

### Recommendation strategy options

`phi view --recommend-for <ref> --recommend-strategy <name>` now supports:

- `golden_rbf`
- `golden_angular`
- `golden_lattice_l1`
- `adaptive_golden_affinity`
- `baseline_rbf`
- `baseline_cosine`

Optional benchmark summary:

- `phi view --benchmark-recommendations`
- `phi view --benchmark-recommendations --recommend-strategy golden_rbf,baseline_rbf`

### Scientific framing (unchanged and explicit)

- `C_STAR_THEORETICAL` remains a theoretical reference from `PHI`,
- `BIO_VACUUM_TARGET` remains **experimental**,
- `HUNTER_C_STATUS` remains **unconfirmed**,
- lattice/adaptive scores are **experimental local similarity utilities**, not empirical proofs.

### Backward compatibility

Recommendation metadata is additive (strategy/score-type fields), and older artifacts without these fields continue to load safely.


## Phase 14.1: Experimental Golden Atlas Navigation

This phase adds `phios.ml.golden_atlas` as an optional local navigation layer over lattice/state-space metadata.

Key points:
- Atlas route costs use monotone increasing travel cost (distance-based), not `(phi/2)^distance` as direct Dijkstra cost.
- Golden decay/coupling remains a similarity annotation, separate from traversal cost.
- Targets supported include:
  - theoretical attractor region around `C_STAR_THEORETICAL`
  - experimental bio band `[BIO_VACUUM_BAND_LOW, BIO_VACUUM_BAND_HIGH]`
  - explicit node targets
- Scientific framing remains explicit: theoretical C* vs experimental bio target and unconfirmed Hunter's C.

CLI additions:
- `phi view --atlas`
- `phi view --atlas --atlas-target theoretical|bio_band|node`
- `phi view --atlas --atlas-node <idx>`
- `phi view --atlas --atlas-start-ref <session_ref>`
- `phi view --atlas --atlas-max-l1-radius <int>`
- `phi view --atlas --atlas-heat-mode target_proximity|path_density|connectivity|bio_band_proximity`

Golden Atlas is experimental and optional local guidance only; it does not alter core PhiKernel truth logic.


## Phase 15: Sector Ontology and Insight Packs

Phase 15 introduces a formal **experimental sector ontology** derived from HG/HB equation scaffolds for observatory UI/analysis context.

### Sector ontology (symbolic/interpretive)

- Added `phios.core.sectors` with HG/HB family sector definitions and metadata.
- This ontology is a symbolic observatory schema and is **not** an empirically validated physical law layer.

### Sector-aware atlas and dashboard surfacing

- Atlas heat modes now include sector-aware options:
  - `geometry_balance`
  - `vacuum_proximity`
  - `observer_entropy`
  - `collector_activity`
  - `mirror_alignment`
  - `emotion_field`
- Dashboard includes sector summary panels based on available local metadata with graceful fallback.

### Insight-pack export

- New export flow:
  - `phi view --export-insight-pack <pathway> <output-dir>`
  - `--insight-pack-title <title>`
  - `--insight-pack-include-atlas`
  - `--insight-pack-heat-mode <mode>`
- Insight packs are static/local bundles with pathway + branch context, sector summaries, recommendations, optional atlas summary, and framing metadata.

### Sector CLI helpers

- `phi view --list-sectors`
- `phi view --list-sectors --sector-family HG`

### Framing reminder

- `C_STAR_THEORETICAL` remains theoretical.
- `BIO_VACUUM_TARGET` and bio band remain experimental.
- `HUNTER_C_STATUS` remains unconfirmed.
- Sector ontology, atlas navigation, and insight packs are optional interpretive/operator layers and do not alter PhiKernel truth logic.


## Phase 16: Branch Replay, Sector Overlays, and Route Compare Bundles

Phase 16 adds branch-aware journey replay, sector overlays in replay/map contexts, richer recommendation diagnostics, and static route-compare bundles.

### Branch-aware replay

- `phi view --branch-replay <pathway>` renders static branch-aware replay context with:
  - current ordered steps
  - outgoing branch labels/notes
  - recommended next-step hints
  - sector overlay summaries

### Route compare bundles

- `phi view --export-route-compare <start-ref> <output-dir>`
- Optional flags:
  - `--route-compare-title <title>`
  - `--route-compare-heat-mode <mode>`
  - `--route-compare-include-sector-overlays`

Export includes static artifacts such as:
- `route_compare_manifest.json`
- `route_compare_index.html`
- `theoretical_route.json`
- `bio_band_route.json`
- `route_diff_summary.json`
- `strategy_diagnostics.json`
- optional `sector_overlay_summary.json`

### Strategy diagnostics

- `phi view --show-strategy-diagnostics <ref>`

Diagnostics remain local exploratory summaries (agreement/overlap behavior), not claims of strategy superiority.

### Scientific framing reminder

- Theoretical attractor routes are reference structures.
- Bio-band routes are experimental guidance structures.
- Hunter’s C remains unconfirmed.
- These overlays/comparisons are interpretive observatory layers and do not alter PhiKernel truth logic.


## Phase 17: Portable Observatory Storyboards

Phase 17 adds static storyboard bundles that combine insight packs, branch replay context, route compare outputs, thematic filters, and comparative summaries.

### Storyboard workflows

- `phi view --create-storyboard <name>`
- `phi view --browse-storyboards`
- `phi view --load-storyboard <name>`
- `phi view --add-to-storyboard <name> --section-type <type> --artifact-ref <ref>`
- `phi view --export-storyboard <name> <output-dir>`

Filter flags:
- `--storyboard-filter-tags <comma,separated>`
- `--storyboard-filter-sector <sector>`
- `--storyboard-filter-type <type>`

### Storyboard export artifacts

- `storyboard_manifest.json`
- `storyboard_index.html`
- `storyboard.json`
- `sections/section_*.json`
- `comparative_summary.json`
- preview metadata and optional integrity hashes

### Comparative report intent

Storyboards and comparative summaries are deterministic local observatory curation layers:
- they do not alter PhiKernel truth logic,
- they do not validate physical laws,
- theoretical attractor references are structural,
- bio-band references are experimental guidance,
- Hunter’s C remains unconfirmed.


## Phase 18: Atlas Gallery, Route Timelines, Sector Snapshots, and Longitudinal Summaries

Phase 18 adds archive-wide atlas gallery views, storyboard-linked route timeline surfacing, sector-comparison dashboard snapshots, and optional longitudinal summary exports over repeated archive artifacts.

### Atlas gallery and longitudinal workflows

- `phi view --atlas-gallery`
- `phi view --export-longitudinal-summary <output-dir>`

Optional filters/titles:
- `--longitudinal-title <title>`
- `--longitudinal-filter-tags <comma,separated>`
- `--longitudinal-filter-sector <sector>`
- `--longitudinal-filter-target <theoretical|bio_band|node>`

### Longitudinal export artifacts

- `longitudinal_manifest.json`
- `longitudinal_index.html`
- `longitudinal_summary.json`
- `sector_snapshot.json`
- `atlas_gallery_summary.json`
- preview metadata and optional integrity hashes

### Scientific framing reminder

- Atlas galleries, route timelines, sector snapshots, and longitudinal summaries are local interpretive curation layers.
- Theoretical attractor references are structural.
- Bio-band references remain experimental guidance.
- Hunter’s C remains unconfirmed.
- None of these reports alter PhiKernel truth logic.


## Phase 19: Cross-Report Observatory Dossiers

Phase 19 adds portable static/local dossier bundles that unify storyboards, route-compare bundles, atlas-gallery outputs, longitudinal summaries, and archive-wide thematic curation into one cross-report navigation layer.

### Dossier workflows

- `phi view --create-dossier <name>`
- `phi view --browse-dossiers`
- `phi view --load-dossier <name>`
- `phi view --add-to-dossier <name> --section-type <type> --artifact-ref <ref>`
- `phi view --export-dossier <name> <output-dir>`

Optional dossier filters:
- `--dossier-tags <comma,separated>`
- `--dossier-filter-tags <comma,separated>`
- `--dossier-filter-sector <sector>`
- `--dossier-filter-type <type>`
- `--dossier-filter-target <theoretical|bio_band|node>`

### Dossier export artifacts

- `dossier_manifest.json`
- `dossier_index.html`
- `dossier.json`
- `sections/section_*.json`
- `dossier_summary.json`
- optional sector/diagnostics/route-context summaries
- preview metadata and optional integrity hashes

### Scientific framing reminder

- Dossiers and curation filters are local interpretive observatory layers.
- Theoretical attractor references are structural.
- Bio-band references remain experimental guidance.
- Hunter’s C remains unconfirmed.
- Dossiers do not alter PhiKernel truth logic.


## Phase 20: Archive-wide Field Libraries

Phase 20 adds static local Field Libraries that organize dossiers, storyboards, route-compare bundles, longitudinal summaries, and related artifacts into reusable thematic collections with lightweight local indexing/navigation.

### Field library workflows

- `phi view --create-field-library <name>`
- `phi view --browse-field-libraries`
- `phi view --load-field-library <name>`
- `phi view --add-to-field-library <name> --section-type <type> --artifact-ref <ref>`
- `phi view --export-field-library <name> <output-dir>`

Optional field-library filters:
- `--field-library-tags <comma,separated>`
- `--field-library-filter-tags <comma,separated>`
- `--field-library-filter-sector <sector>`
- `--field-library-filter-type <type>`
- `--field-library-filter-target <theoretical|bio_band|node>`

### Field library export artifacts

- `field_library_manifest.json`
- `field_library_index.html`
- `field_library.json`
- `collections/collection_*.json`
- `field_library_summary.json`
- optional sector/diagnostics/route-context summaries
- preview metadata and optional integrity hashes

### Scientific framing reminder

- Field libraries and thematic collections are local interpretive observatory layers.
- Theoretical attractor references are structural.
- Bio-band references remain experimental guidance.
- Hunter’s C remains unconfirmed.
- Field libraries do not alter PhiKernel truth logic.

## Phase 21: Observatory Shelves + Cross-Library Catalog

Phase 21 adds additive, static/local Observatory Shelves and cross-library Catalog views that sit above field libraries, dossiers, storyboards, and related observatory artifacts for archive-scale browsing.

### Shelf workflows

- `phi view --create-shelf <name>`
- `phi view --browse-shelves`
- `phi view --load-shelf <name>`
- `phi view --add-to-shelf <name> --section-type <type> --artifact-ref <ref>`
- `phi view --export-shelf <name> <output-dir>`

Optional shelf filters/tags:
- `--shelf-title <title>`
- `--shelf-summary <summary>`
- `--shelf-tags <comma,separated>`
- `--shelf-filter-tags <comma,separated>`
- `--shelf-filter-sector <sector>`
- `--shelf-filter-type <type>`

### Catalog workflows

- `phi view --browse-catalog`
- `phi view --browse-catalog --catalog-filter-tags <comma,separated>`
- `phi view --browse-catalog --catalog-filter-sector <sector>`
- `phi view --browse-catalog --catalog-filter-type <type>`
- `phi view --browse-catalog --catalog-group-by <artifact_type|collection|sector_family|dominant_sector|target_mode|heat_mode|has_bio|has_diagnostics>`
- `phi view --browse-catalog --output <path.html>` (static local catalog page)

### Shelf export artifacts

- `shelf_manifest.json`
- `shelf_index.html`
- `shelf.json`
- `items/item_*.json`
- `shelf_summary.json`
- optional sector/diagnostics/route-context summaries
- preview metadata and optional integrity hashes

### Scientific framing reminder

- Shelves, catalogs, collections, route comparisons, and longitudinal summaries are local observatory interpretation and curation only.
- `C_STAR_THEORETICAL = PHI / 2 = (1 + sqrt(5)) / 4` is a structural/theoretical reference.
- `BIO_VACUUM_TARGET = 0.81055` with `[BIO_VACUUM_BAND_LOW, BIO_VACUUM_BAND_HIGH] = [0.807, 0.813]` remains experimental guidance.
- `BIO_VACUUM_STATUS = "experimental"` and `HUNTER_C_STATUS = "unconfirmed"` remain explicit.
- Shelf/catalog layers do not alter PhiKernel truth logic.

### Backward compatibility note

Older field libraries, dossiers, storyboards, route-compare bundles, longitudinal summaries, insight packs, pathways, atlas exports, sessions, compare sets, narratives, and constellations continue loading with safe defaults even when shelf/catalog metadata is absent.

## Phase 22: Observatory Reading Rooms + Themed Collection Maps

Phase 22 adds additive, static/local Reading Rooms and Collection Maps above shelves/field libraries to provide curated archive entry points with deterministic metadata navigation.

### Reading room workflows

- `phi view --create-reading-room <name>`
- `phi view --browse-reading-rooms`
- `phi view --load-reading-room <name>`
- `phi view --add-to-reading-room <name> --section-type <type> --artifact-ref <ref>`
- `phi view --export-reading-room <name> <output-dir>`

Optional reading-room fields:
- `--reading-room-title <title>`
- `--reading-room-summary <summary>`
- `--reading-room-tags <comma,separated>`

### Collection map workflows

- `phi view --create-collection-map <name>`
- `phi view --browse-collection-maps`
- `phi view --load-collection-map <name>`
- `phi view --export-collection-map <name> <output-dir>`
- `--collection-map-tags <comma,separated>`
- `--collection-map-filter-tags <comma,separated>`
- `--collection-map-filter-sector <sector>`
- `--collection-map-filter-type <type>`
- `--collection-map-group-by <field>`

### Reading room export artifacts

- `reading_room_manifest.json`
- `reading_room_index.html`
- `reading_room.json`
- `sections/section_*.json`
- `reading_room_summary.json`
- optional sector/diagnostics/route-context summaries
- preview metadata and optional integrity hashes

### Collection map export artifacts

- `collection_map_manifest.json`
- `collection_map_index.html`
- `collection_map.json`
- `collection_map_summary.json`
- preview metadata and optional integrity hashes

### Scientific framing reminder

- Reading rooms, collection maps, shelves, catalogs, and downstream curation artifacts remain local interpretive layers only.
- `C_STAR_THEORETICAL = PHI / 2 = (1 + sqrt(5)) / 4` is structural/theoretical framing.
- `BIO_VACUUM_TARGET = 0.81055` and `[BIO_VACUUM_BAND_LOW, BIO_VACUUM_BAND_HIGH] = [0.807, 0.813]` remain experimental guidance.
- `BIO_VACUUM_STATUS = "experimental"` and `HUNTER_C_STATUS = "unconfirmed"` remain explicit.
- These layers do not alter PhiKernel truth logic.

### Backward compatibility note

Older artifacts (field libraries, dossiers, storyboards, route-compare bundles, longitudinal summaries, insight packs, pathways, atlas exports, sessions, compare sets, narratives, constellations, shelves, catalogs) continue loading with safe defaults even when reading-room/collection-map metadata is absent.

## Phase 23: Observatory Study Halls + Comparative Thematic Pathways

Phase 23 adds additive, static/local Study Halls and Thematic Pathways above reading rooms and collection maps to support archive-wide learning/exploration with deterministic metadata navigation.

### Study hall workflows

- `phi view --create-study-hall <name>`
- `phi view --browse-study-halls`
- `phi view --load-study-hall <name>`
- `phi view --add-to-study-hall <name> --section-type <type> --artifact-ref <ref>`
- `phi view --export-study-hall <name> <output-dir>`
- `--study-hall-title <title>`
- `--study-hall-summary <summary>`
- `--study-hall-tags <comma,separated>`

### Comparative thematic pathway workflows

- `phi view --create-thematic-pathway <name>`
- `phi view --browse-thematic-pathways`
- `phi view --load-thematic-pathway <name>`
- `phi view --export-thematic-pathway <name> <output-dir>`
- `--thematic-pathway-tags <comma,separated>`
- `--thematic-pathway-filter-tags <comma,separated>`
- `--thematic-pathway-filter-sector <sector>`
- `--thematic-pathway-filter-type <type>`
- `--thematic-pathway-group-by <field>`

### Study hall export artifacts

- `study_hall_manifest.json`
- `study_hall_index.html`
- `study_hall.json`
- `modules/module_*.json`
- `study_hall_summary.json`
- optional sector/diagnostics/route-context summaries
- preview metadata and optional integrity hashes

### Thematic pathway export artifacts

- `thematic_pathway_manifest.json`
- `thematic_pathway_index.html`
- `thematic_pathway.json`
- `thematic_pathway_summary.json`
- preview metadata and optional integrity hashes

### Scientific framing reminder

- Study halls, thematic pathways, reading rooms, collection maps, shelves, catalogs, and related curation artifacts are local observatory interpretation only.
- `C_STAR_THEORETICAL = PHI / 2 = (1 + sqrt(5)) / 4` remains structural/theoretical framing.
- `BIO_VACUUM_TARGET = 0.81055` and `[BIO_VACUUM_BAND_LOW, BIO_VACUUM_BAND_HIGH] = [0.807, 0.813]` remain experimental guidance.
- `BIO_VACUUM_STATUS = "experimental"` and `HUNTER_C_STATUS = "unconfirmed"` remain explicit.
- These layers do not alter PhiKernel truth logic.

### Backward compatibility note

Older reading rooms, collection maps, field libraries, dossiers, storyboards, route-compare bundles, longitudinal summaries, insight packs, pathways, atlas exports, sessions, compare sets, narratives, constellations, shelves, and catalogs continue loading with safe defaults when study-hall/thematic-pathway metadata is absent.

## Phase 24: Observatory Curricula + Comparative Journey Ensembles

Phase 24 adds additive, static/local Curricula and Comparative Journey Ensembles above study halls and thematic pathways to support reusable archive-wide learning tracks and deterministic comparative exploration.

### Curriculum workflows

- `phi view --create-curriculum <name>`
- `phi view --browse-curricula`
- `phi view --load-curriculum <name>`
- `phi view --add-to-curriculum <name> --section-type <type> --artifact-ref <ref>`
- `phi view --export-curriculum <name> <output-dir>`
- `--curriculum-title <title>`
- `--curriculum-summary <summary>`
- `--curriculum-tags <comma,separated>`

### Comparative journey ensemble workflows

- `phi view --create-journey-ensemble <name>`
- `phi view --browse-journey-ensembles`
- `phi view --load-journey-ensemble <name>`
- `phi view --export-journey-ensemble <name> <output-dir>`
- `--journey-ensemble-tags <comma,separated>`
- `--journey-ensemble-filter-tags <comma,separated>`
- `--journey-ensemble-filter-sector <sector>`
- `--journey-ensemble-filter-type <type>`
- `--journey-ensemble-group-by <field>`

### Curriculum export artifacts

- `curriculum_manifest.json`
- `curriculum_index.html`
- `curriculum.json`
- `units/unit_*.json`
- `curriculum_summary.json`
- optional sector/diagnostics/route-context summaries
- preview metadata and optional integrity hashes

### Journey ensemble export artifacts

- `journey_ensemble_manifest.json`
- `journey_ensemble_index.html`
- `journey_ensemble.json`
- `journey_ensemble_summary.json`
- preview metadata and optional integrity hashes

### Scientific framing reminder

- Curricula, comparative journey ensembles, study halls, thematic pathways, reading rooms, collection maps, shelves, catalogs, and related curation artifacts are local observatory interpretation only.
- `C_STAR_THEORETICAL = PHI / 2 = (1 + sqrt(5)) / 4` remains structural/theoretical framing.
- `BIO_VACUUM_TARGET = 0.81055` and `[BIO_VACUUM_BAND_LOW, BIO_VACUUM_BAND_HIGH] = [0.807, 0.813]` remain experimental guidance.
- `BIO_VACUUM_STATUS = "experimental"` and `HUNTER_C_STATUS = "unconfirmed"` remain explicit.
- These layers do not alter PhiKernel truth logic.

### Backward compatibility note

Older study halls, thematic pathways, reading rooms, collection maps, field libraries, dossiers, storyboards, route-compare bundles, longitudinal summaries, insight packs, pathways, atlas exports, sessions, compare sets, narratives, constellations, shelves, and catalogs continue loading with safe defaults when curriculum/journey-ensemble metadata is absent.

## Phase 25: Observatory Syllabi + Comparative Atlas Cohorts

Phase 25 adds additive, static/local Syllabi and Comparative Atlas Cohorts above curricula and journey ensembles to support reusable program-level tracks and deterministic cross-sequence comparison.

### Syllabus workflows

- `phi view --create-syllabus <name>`
- `phi view --browse-syllabi`
- `phi view --load-syllabus <name>`
- `phi view --add-to-syllabus <name> --section-type <type> --artifact-ref <ref>`
- `phi view --export-syllabus <name> <output-dir>`
- `--syllabus-title <title>`
- `--syllabus-summary <summary>`
- `--syllabus-tags <comma,separated>`

### Comparative atlas cohort workflows

- `phi view --create-atlas-cohort <name>`
- `phi view --browse-atlas-cohorts`
- `phi view --load-atlas-cohort <name>`
- `phi view --export-atlas-cohort <name> <output-dir>`
- `--atlas-cohort-tags <comma,separated>`
- `--atlas-cohort-filter-tags <comma,separated>`
- `--atlas-cohort-filter-sector <sector>`
- `--atlas-cohort-filter-type <type>`
- `--atlas-cohort-group-by <field>`

### Syllabus export artifacts

- `syllabus_manifest.json`
- `syllabus_index.html`
- `syllabus.json`
- `modules/module_*.json`
- `syllabus_summary.json`
- optional sector/diagnostics/route-context summaries
- preview metadata and optional integrity hashes

### Atlas cohort export artifacts

- `atlas_cohort_manifest.json`
- `atlas_cohort_index.html`
- `atlas_cohort.json`
- `atlas_cohort_summary.json`
- preview metadata and optional integrity hashes

### Scientific framing reminder

- Syllabi, atlas cohorts, curricula, journey ensembles, study halls, thematic pathways, reading rooms, collection maps, shelves, catalogs, and related curation artifacts are local observatory interpretation only.
- `C_STAR_THEORETICAL = PHI / 2 = (1 + sqrt(5)) / 4` remains structural/theoretical framing.
- `BIO_VACUUM_TARGET = 0.81055` and `[BIO_VACUUM_BAND_LOW, BIO_VACUUM_BAND_HIGH] = [0.807, 0.813]` remain experimental guidance.
- `BIO_VACUUM_STATUS = "experimental"` and `HUNTER_C_STATUS = "unconfirmed"` remain explicit.
- These layers do not alter PhiKernel truth logic.

### Backward compatibility note

Older curricula, journey ensembles, study halls, thematic pathways, reading rooms, collection maps, field libraries, dossiers, storyboards, route-compare bundles, longitudinal summaries, insight packs, pathways, atlas exports, sessions, compare sets, narratives, constellations, shelves, and catalogs continue loading with safe defaults when syllabus/atlas-cohort metadata is absent.
